From values to names
Instead of using #FACB2E in forty places, you define a token like color.brand.accent and use that name everywhere. When the accent changes, you update one value. Designers see the name in their tools and developers see it in code.
Three layers
| Layer | Example | Purpose |
|---|---|---|
| Primitive | gold-500 = #FACB2E | The raw palette and scales |
| Semantic | color.action.primary = gold-500 | The role a value plays in the interface |
| Component | button.primary.background = color.action.primary | A specific part of the UI |
Most teams get the biggest benefit from the semantic layer. It is what lets you swap a theme by pointing roles at different primitives.
What to turn into tokens
- Color: brand, text, background, border, status.
- Typography: families, sizes, weights, line heights.
- Spacing: a scale such as 4, 8, 12, 16, 24, 32.
- Radius, border width, and shadow.
- Motion: durations and easing curves.
A standard format
The Design Tokens Community Group, a W3C community group, released the first stable version of its Design Tokens Format Module (2025.10) in October 2025. It defines a JSON format so that tools can exchange tokens. Tools such as Style Dictionary, Tokens Studio, and Terrazzo support it. Note that this is a Community Group report, not a W3C Recommendation, but it gives teams a shared target.
Put tokens to work
Define
Name tokens in one source of truth, in design tools or in JSON.
Transform
Use a build tool like Style Dictionary to output CSS variables, iOS, and Android values.
Consume
Components reference tokens, never raw values.
Govern
Review new tokens and remove unused ones.



