Design
3 min read
Design systems that survive contact with engineering
A component library is only useful if it encodes decisions. Token-first systems age far better than page-level design files.
JW
By James Whitfield
The design systems that last share one trait: they encode decisions, not pixels. Spacing, colour and type are defined once as tokens; components consume tokens rather than hardcoded values.
What we put in the first version
- A colour palette with semantic names, not
blue-500 - A type scale using fluid
clamp()values - Focus states defined alongside hover states
- Two or three layout primitives instead of twelve card variants
Accessibility is not a later phase. Contrast, focus visibility and reduced-motion handling belong in the tokens, because that is the only place you can enforce them.