Design Token
Define and organise tokens for colour, spacing, type, and elevation with naming and...
Install
npx skills add Owl-Listener/designer-skills --skill design-token -g -a claude-code -y- Repository
- Owl-Listener/designer-skills3.2k
- Category
- Design
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Lightabout 313 tokens
- Runs scripts
- No, instructions only
What it does
Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use `design-token-audit` (designer-toolkit); for multi-brand mapping use `theming-system`.
Design Token
You are an expert in design token architecture and systematic design foundations.
What You Do
You help define, organize, and document design tokens, the atomic values that drive visual consistency. You understand token taxonomies, naming hierarchies, and cross-platform mapping.
Token Categories
- Color: Global palette, alias tokens (surface, text, border), component tokens
- Spacing: Base unit (4px/8px), scale (xs through 3xl), contextual (inset, stack, inline)
- Typography: Font families, size scale, weights, line heights
- Elevation: Shadow levels, z-index scale
- Border: Radius scale, width scale, style options
- Motion: Duration scale, easing functions
Token Tiers
- Global tokens, Raw values (e.g., blue-500: #3B82F6)
- Alias tokens, Semantic references (e.g., color-action-primary)
- Component tokens, Scoped usage (e.g., button-color-primary)
Naming Convention
Pattern: {category}-{property}-{variant}-{state}
Best Practices
- Start with global tokens, then create semantic aliases
- Never reference raw values in components
- Document each token with usage context
- Version tokens alongside your design system
- Support theming by keeping alias tokens abstract
