brandkit

Skill: Brand Kit

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

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.

Skill: Brand Kit

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

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.