Type is more than style. Treating it as shared infrastructure through design tokens keeps products consistent and makes redesigns far less painful.
Tokens over values
Instead of hard-coding sizes and weights, name them by purpose: heading, body, caption. Components consume the names, and the values can change in one place.
Make it responsive by default
Fluid scales reduce the number of breakpoints designers and developers need to maintain while keeping rhythm and readability intact.
- Define a small, purposeful scale.
- Document usage with real examples.
- Version tokens like any other shared package.
