Skip to content
Design
Skill

/brandkit

Generate a complete, accessible brand design system from a brief, as primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css, verified for WCAG. Use when the user wants a from-scratch brand/design

From plugin
ux-ui-agent-skills
3.1k26 skills1 agent1 command3 hooks
+1

Claude Code

$ npx -y skills add plugin87/ux-ui-agent-skills --skill brandkit --agent claude-code

SKILL.md

brandkit.SKILL.md
name: brandkit
description: Generate a complete, accessible brand design system from a brief, as primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css, verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.
# `invocation:` was not a field Claude Code reads - unknown frontmatter keys are
# ignored without an error, so these six were auto-invocable the whole time they
# were marked user-only. This is the field that actually does it.
disable-model-invocation: true

Skill: Brand Kit

Requirements

This skill needs the full UX/UI Agent Skills kit: the gates, the references and the design-system library. Install it with `npx ux-ui-agent-skills@3.1.0 init` or as the Claude Code plugin. `npx skills@1.7.6 add` copies the skill folder and nothing else. Installed that way, this skill runs in **guidance-only mode**: no gate runs, so it gives no verdict.

> **Step 0: is the kit here?** Check once: > `ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING` > On `KIT_MISSING`, open your reply with: "Guidance-only mode: the UX/UI Agent > Skills kit is not installed here, so no gate ran and nothing below is > measured." Then work from this file and general practice, under three rules. > Do not guess or cite the contents of a kit file you could not open. State no > measured number (no contrast ratio, no N/N, no "passes WCAG"): write "not > verified" where one would go. End with a line `Skipped (kit not installed):` > that names every gate script this file tells you to run, then the install > command above.

Stand up the *foundation* (one token system everything renders from) before any screen. Get this right and every page stays consistent and themeable from one place.

Steps

1. **Brief Inference (mandatory)**: name the industry, audience, the one mood adjective, and motion depth (`${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md` → Brief Inference). Pick an anchoring archetype from `${CLAUDE_SKILL_DIR}/../../../taste/aesthetic-systems.md`. 2. **Primitives**: generate the brand color ramp in **OKLCH** (11 shades, consistent chroma) + a neutral ramp; verify the 500 shade ≥ 4.5:1 on white (text) and 600 ≥ 3:1 (UI) per `${CLAUDE_SKILL_DIR}/../../../.claude/rules/tokens-and-color.md` → Color Generation. 3. **Semantic layer**: map roles to primitives (`action.primary`/`-hover`/`destructive`, `text.{primary,secondary,on-action,link}`, `surface.{page,card,raised}`, `border.{default,strong}`, `feedback.{success,warning,error,info}`), and the **dark** overrides (designed, not inverted). 4. **Scales**: Major Third type scale + composite text styles, 4px spacing scale, radius tiers, elevation, and `${CLAUDE_SKILL_DIR}/../../../tokens/motion.json`-style durations/easings. 5. **Emit** the DTCG `${CLAUDE_SKILL_DIR}/../../../tokens/*.json` (3-tier) + a single `theme.css` (the one shared source, `[data-theme="dark"]` overrides). Optionally feed the token-build pipeline (`token-build` skill) for other platforms.

Verification (definition of done)

  • `python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py`: valid JSON, all aliases resolve.
  • `python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.py`: required text/action/border pairs pass WCAG AA in **light AND dark**; `border.strong` ≥ 3:1.
  • `python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_theme_refs.py`: every component `var(--…)` resolves to the theme.
  • One theme, no per-page palettes; destructive = danger token (not primary); zero hardcoded values.

> Output is a verified token foundation: the measurable part is provable (run `npm run verify`). Brand "feel" still benefits from a human review against `${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md`.

Read more
@plugin87
Ships withux-ui-agent-skills

aka XIAS

3.1k26 skills1 agent2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
3.1k
Star history of plugin87/ux-ui-agent-skills on GitHub, a chart by star-history.com

Other skills on ux-ui-agent-skills.

a11y-audit

a11y-audit

Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and…

critique

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green,…

design-code

design-code

Generate production-ready, accessible, token-driven component code for ANY framework (React+Tailwind, Next.js, SwiftUI, Vue,…

More skills from other plugins.

impeccable

impeccable

Use to design, redesign, critique, audit, polish or animate a frontend: websites, landing pages, dashboards, app UI, components,…

@pbakaus@pbakausInstall Skill

Questions about brandkit.

Which coding agents can use brandkit?
brandkit installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.