brand-to-tokens

# brand-to-tokens > The brand→token derivation — the **first consumer demand** that closes the > ADR-061 §8 deferral. Takes a confirmed [`brand-identity`](../brand-identity/SKILL.md) > constraint set and produces a DTCG `.tokens.json` **source of truth**, then > hands it to the [`design-tokens`](../design-tokens/SKILL.md) toolchain to emit > CSS vars + Tailwind. The same `.tokens.json` is the export that pack-ai-image > brand-asset generation and the greenfield scaffold seed consume (B → A; > contract: [`brand-token-consumption`](../../../docs/contracts/brand-token-consumption.md)). ## When to use - A confirmed brand identity (colour story, type story, spacing) needs to become a maintained token system. - A consumer asks to "turn the brand into tokens / CSS variables / a theme." - Before pack-ai-image brand-asset generation or a greenfield scaffold needs the `.tokens.json` export. ## Procedure 1. **Take the confirmed brand-identity constraint set** — colour story (roles + values), type story (heading/body classes), spacing/radius intent. If a consumer brand profile already registers values, those win ([`brand-source-of-truth`](../../rules/brand-source-of-truth.md)). 2. **Author `.tokens.json`** on the `design-tokens` 3-layer DTCG model (`$value` / `$type`): brand palette → `primitive.color.*`; brand roles (primary, accent, surface, destructive) → `semantic.color.*` referencing the primitives; per-widget needs → `component.*`. Add `dark.semantic.*` o...