Richie
732c872576
Token pipeline (Style Dictionary v4, DTCG format): - Primitive tokens: colour palettes (brand, sage, neutral, feedback), typography (3 font families, 21-variant type scale), spacing (4px grid), border radius, shadows, opacity - Semantic tokens: text, surface, border, interactive, feedback colours; typography roles; layout spacing - Component tokens: Button (4 sizes), Input (2 sizes) - Generated outputs: CSS custom properties, JS ES6 module, flat JSON Atoms (3 components): - Button: contained/soft/outlined/text × primary/secondary, 4 sizes, loading state, underline for text variant - Typography: 21 variants across display/heading/body/label/caption/overline, maxLines truncation - Input: external label, helper text, error/success validation, start/end icons, required indicator, 2 sizes, multiline support Infrastructure: - MUI v5 theme with full token mapping - Storybook 8 with autodocs - Claude Code agents and skills for token/component workflows - Design system documentation and cross-session memory Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
859 B
859 B
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| create-tokens | Create design tokens from brand colours, fonts, and reference material | [brand colours, fonts, or Figma URL] |
Create design tokens for the FA Design System.
Use the token-architect agent to handle this task. The user's input follows — it may include brand colours, font choices, reference images, or Figma URLs.
Instructions for the agent:
- Read all memory files and conventions before starting
- If the user provides a Figma URL, use the Figma MCP to extract design context
- Create primitive tokens (colour scales, typography, spacing, effects)
- Create semantic tokens (map primitives to design intent)
- Run
npm run build:tokensto generate outputs - Update the MUI theme in
src/theme/index.tsto use generated values - Update all memory files when done
User input: $ARGUMENTS