Design Token

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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

Instructions onlyDesign & Creative
AI-generated overview

Defines and organizes design tokens for color, spacing, typography, elevation, border, and motion.

What it does
This skill provides guidance for defining, organizing, and documenting design tokens as the atomic values behind visual consistency. It covers token categories, three token tiers (global, alias, component), a naming pattern, and best practices for aliasing, documentation, versioning, and theming. It produces token definitions and usage rules rather than files or code.
When to use it
Use it when establishing the token layer of a design system, such as setting up color, spacing, type, and elevation values with naming and usage rules. It is not intended for auditing existing token usage or for multi-brand mapping, which the skill points to other skills for.
Requirements
No tools, packages, runtimes, credentials, or network access are required; it is instructions only and ships no scripts.

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

Source and attribution

Source:owl-listener/designer-skillsindesign-systems/skills/design-tokenat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Design Token Agent Skill | SourceWeft