CtrlK
BlogDocsLog inGet started
Tessl Logo

design-token

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`.

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-systems/skills/design-token/SKILL.md
SKILL.md
Quality
Evals
Security

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

  1. Global tokens — Raw values (e.g., blue-500: #3B82F6)
  2. Alias tokens — Semantic references (e.g., color-action-primary)
  3. 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
Repository
Owl-Listener/designer-skills
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.