base-tokenslisted
Install: claude install-skill robertoDon/studio
# Tokens · Few values, each with a name
Sources: W3C Design Tokens Community Group (Format Module); Material Design 3 (design tokens: reference, system, component); Salesforce Lightning (where the term came from, Jina Anne); Nathan Curtis, "Naming Tokens in Design Systems" (EightShapes). A screen with a generated look has stray values. Tokens close the books: if a value has no name, it doesn't go in.
## The direction document
The project's art direction lives in **`DESIGN.md` at the root** of the repository. Its format is in `skills/art-direction/references/design-md.md`. Tokens are its technical translation: DESIGN.md says *why* and *which school*; tokens say *how much*. When DESIGN.md changes, update the tokens in the same commit.
## Three layers
| Layer | What it is | Example | Who uses it |
|---|---|---|---|
| **Primitive** (reference) | The raw value, no meaning | `--green-600: oklch(0.52 0.17 150)` · `--space-4: 16px` | Only the semantic layer |
| **Semantic** (system) | The value's role | `--color-action` · `--color-text-mute` · `--space-stack` | Components and screens |
| **Component** | A decision for one component | `--button-radius` · `--card-padding` | Only that component |
Rule: **a component never reads a primitive**. Switching theme (light/dark) or brand (another product) changes only the semantic layer.
## What becomes a token
| Group | Minimum tokens |
|---|---|
| Color | bg, surface, surface-raised, text, text-mute, border, action, on-action, focus,