Skip to content
SkillScript-led849 tokens in use

Brand

Keep brand voice, visual identity and messaging in one guidelines file, then sync it to design tokens and check assets against it.

152,128 stars on the repository MIT Licensenextlevelbuilder/ui-ux-pro-max-skill · cli/assets/skills/brand
npm install -g ui-ux-pro-max-cli uipro init --ai claude
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Brand costs

35tokens idle
849tokens in use
13,446tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/extract-colors.cjs, scripts/inject-brand-context.cjs, scripts/sync-brand-to-tokens.cjs, scripts/tests/test_sync_brand_to_tokens.py, scripts/validate-asset.cjs.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure23/25
  • Examples12/15
  • Output10/15
  • Size10/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 31
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/sync-brand-to-tokens.cjs, line 393

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity36
  • Momentum40

Brand covers voice, visual identity, messaging frameworks, asset management and consistency reviews. Its source of truth is a brand guidelines file in the project, and four Node scripts turn that file into prompt context, design tokens, asset checks and color comparisons.

Reference documents cover voice, messaging, logo usage, color palettes, typography, asset organization and approval checklists, and a starter template gives a new brand a complete guidelines file to fill in.

What You Get

  • Four Node scripts for brand context injection, token sync, asset validation and color extraction
  • Ten reference documents on voice, visual identity, messaging, logos, colors, typography, assets and approvals
  • A starter brand guidelines template for new brands
  • A sync flow from docs/brand-guidelines.md to assets/design-tokens.json and design-tokens.css
  • An update subcommand for revising the brand and syncing it to design systems

Common Use Cases

  • Writing a first brand guidelines file for a new product
  • Keeping marketing copy in a consistent voice by injecting brand context into prompts
  • Auditing logos and images for naming, size and format rules
  • Turning brand colors and fonts into CSS variables without hand copying

What Makes It Unique

Many brand skills are style advice only. This one connects the guidelines file to code: a single sync produces token JSON and CSS, and the sync stops when it finds an existing token setup, CSS custom properties or a Tailwind theme, so it does not overwrite a design system the project already has. It also serves as the first stage of the repository’s wider design workflow, feeding the design-system and ui-styling skills.

Under The Hood

The model reads SKILL.md and the references it needs, then runs Node scripts from the skill folder with the project as the working directory. The scripts read the brand guidelines and project files, and the sync script writes token JSON and CSS into the assets folder and calls the design-system token generator as a child process. It refuses to proceed when it detects existing token or theme files unless force is passed. No network calls are made.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers