Tokenization
Change one value, over 200+ components repaint
United's design system - had design tokens, but components still hard-coded their own colors and spacing, so a brand change meant editing them one at a time. I rebuilt it as layers. The brand now changes in one place, and theming is a swap rather than a second stylesheet.
- 200+
- Components migrated
- 40+
- Teams downstream
- Brand consistency
- Impact
The problem
A design system with over 200 components will still drift if each component hard-codes its own values. The tokens existed, but components reached past them to raw variables and literals - so a brand change meant touching the component layer, and theming could not be expressed at all. The layer was there; nothing forced anything through it.
What I built
Three layers - raw values, then meaning, then per-component sets - so a component asks for intent (space, surface) and never a literal
Style Dictionary compiles one JSON source into SCSS, CSS custom properties, and platform outputs, replacing an older pipeline
A theme layer above meaning, which is what makes light and dark a token swap instead of a parallel stylesheet
What changed
- over 200 components migrated onto tokens in one rollout
- Semantic spacing replaced per-component literals
- A value now propagates without editing a single component
Stack
- React
- TypeScript
- Style Dictionary
- SCSS
- Storybook
- Figma Code Connect
- Accessibility (WCAG 2.0 / ADA)
- Claude Code