Token Discipline

What it is. Token discipline is the rule that every visible value in a design file, color, spacing, type, radius, shadow, motion, must resolve to a semantic token from a single source of truth. No local styles. No hard-coded hex or pixels. A button background does not sit at #3B82F6. It sits at color/background/brand-primary. A card radius does not sit at 12. It sits at radius/container. Typography pulls from font-size/heading-1, font-weight/semibold, line-height/tight. This makes the entire file machine-readable for developers and 2026 coding agents. The parent article calls tokens the load-bearing wall of the four-layer system. Components sit on tokens. Patterns sit on components. Pages sit on patterns. Break the foundation and the whole handoff becomes approximation layered on approximation. Three rules keep it alive. Every value resolves with zero exceptions. Names stay semantic so surface/raised survives a full rebrand while gray-200 does not. One library acts as single source of truth, exported once and consumed everywhere. Figma Variables or Tokens Studio enforces it. When MCP reads the file the agent pulls exact values instead of guessing. The result is compilation, not translation.

What it isn't. Token discipline is not dropping a few brand colors into Figma Variables then calling the file clean. It is not naming tokens after literal appearance like blue-500 or padding-24. It is not a final polish step applied the night before handoff. It is not optional for any team touching Claude Code, Cursor, or modern MCP workflows. It is not the same as having nice components while letting loose elements run wild on actual pages. Plenty of teams run theater where 60 percent of values sit outside the token set as overrides. That produces the same old drift, just faster. It is not a maturity signal for senior designers only. Junior designers need it most because it removes decision fatigue before they develop bad habits. Skip the discipline and your perfect component library still ships gruyere interfaces full of one-off values that no QA checklist can catch at scale.

Concrete example. A fintech team rebuilding their mobile banking app in Q1 2025 started with 43 different grays and 19 shades of brand blue scattered across screens. Handoff produced 312 clarification questions in the first two sprints. After enforcing token discipline they defined 14 neutral tokens including content/primary, content/muted, content/subtle, border/default, surface/base, surface/raised. Brand tokens split into color/background/brand-primary, color/background/brand-primary-hover, color/content/inverse. Every button, input, divider, and nav item resolved to these. Radius used radius/input-sm and radius/button-lg consistently. Motion tokens covered duration/fast, duration/slow, easing/spring, easing/linear. The Claude agent wired through MCP generated React Native components that matched production variables on first pass. Implementation time dropped from 19 days to 6. Visual QA went from 47 logged issues to 4. Another team at a Linear-like B2B tool applied the same rules to their command menu. Shadow tokens elevation/low, elevation/mid, elevation/high replaced manual blur and offset values. The entire product switched from one shadow style to a softer new one by editing three tokens at the root. No developer had to hunt through files. A third case hit a Stripe-shaped checkout flow where the destructive button referenced color/background/danger instead of a hardcoded red. When legal required a higher contrast red the change took 90 seconds and touched every instance across web and mobile. These teams stopped treating tokens as decoration and started treating them as the contract. The file became the spec.

When to use it. Use token discipline on any file destined for production, any design system component, any pattern library, or any handoff that will touch Claude Code, Cursor, MCP, or Code Connect. Use it the moment more than two designers touch the same codebase. Use it before you build your first responsive pattern so breakpoints inherit correct spacing scales. Use it when you want visual QA to take 30 minutes instead of three days. Do not use it on pure exploration artboards, pitch decks, one-off marketing pages updated twice a year, or internal prototypes that die after one demo. Do not force it onto a legacy project shipping next Tuesday if the migration cost exceeds the remaining runway. The discipline pays for itself only when repetition, maintenance, and AI consumption are part of the workflow.

Token discipline turns your Figma file from a suggestion into a specification that ships without translation errors.