Design Token
A named, reusable value for a design decision — a color, spacing unit, font size, or radius — stored centrally so it stays consistent across platforms.
Why it matters
Tokens are decisions with names: change the accent token once and every button, link and chip agrees. They are also the bridge to code — the same token feeds the design file and the build, so drift becomes impossible by construction.
See it
One named decision, consumed everywhere — change the token and every consumer agrees at once.
The numbers
- Name by role, not value — color-danger, never red-500-ish
- One source — the file and the codebase read the same token
Related terms
Ask your assistant
Define "Design Token" using uxspot. Works in Claude, Cursor or any MCP client — connect the uxspot MCP.
Think it stuck? A 20-second round of Spot Check will tell you.