Skip to main content

Core Concepts

A quick rundown of the main ideas in Token Designer before you dig in.

Design tokens

A design token is just a named value for a design decision. Instead of hardcoding #16A34A in fifty places across your codebase, you define one token called color.success.500 and use that name everywhere. When the color needs to change, you change it once.

Tokens can represent colors, sizes, spacing, font families, font weights, animation durations, and more.

Token types

Every token has a type that tells the app (and any downstream tools) what kind of value it is.

TypeWhat it's for
ColorHex, RGB, or other color values
DimensionSizes, spacing, radii, anything measured in px or rem
Font FamilyFont stack names
Font WeightNumeric or named weights like 400, 700, or Semi
DurationAnimation and transition times
NumberPlain numbers with no unit

Groups

Tokens live inside groups, which work like folders. They show up as a collapsible tree in the left sidebar and can be nested as deep as you need.

Most projects split tokens into two layers:

  • Base tokens — the raw palette, like every shade of a color from 50 to 900
  • Semantic tokens — tokens that point to base tokens and describe their role, like color.success referencing color.green.500

Contexts and themes

A context is a named variant of your token values. Every project starts with one called default. You can add more (like light and dark) and then override specific tokens per context without touching the defaults.

When you switch to a non-default context, the token table shows a Default Value column next to a Value column. Leave the value blank and the token inherits from default. Set one and it overrides. That's the whole system.

Design Guides

The Design Guides are built-in workflows for setting up the common parts of your token system: color palettes, type scales, border radii, spacing. Rather than typing in raw values yourself, you get sliders, presets, and pickers that generate the tokens for you.

Publishing and exporting

Two ways to get your tokens out:

  • Download — grabs the current project state as a file, right now, no version attached
  • Publish a release — creates a versioned snapshot like v0.1.0 with release notes that developers can reference or roll back to

See Publishing & Releases for more.