mcpField
B
brandkit

brandkit

github.com/plugin87Design & UI3.1k529 installsUpdated 3d ago
Repository

About brandkit

brandkit is a skill for establishing a shared design-token foundation before building screens. It guides color, semantic roles, scales, dark-theme overrides, and token output, with validation for contrast and references.

Key features

  1. 01Infer audience, industry, and visual direction
  2. 02Generate OKLCH color and neutral ramps
  3. 03Define semantic tokens and dark overrides
  4. 04Create type, spacing, radius, and motion scales
  5. 05Emit DTCG token files and theme.css
  6. 06Validate tokens and contrast

Use cases

  1. 01Creating a shared token foundation for a project
  2. 02Setting up light and dark theme values
  3. 03Generating reusable design scales before screen work
  4. 04Checking token references and WCAG contrast

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill brandkit

After installing, type/brandkitin Claude Code to confirm it loaded.

Details

From the project README

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.

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.

Comments

Markdown supported