HOW TO SCALE DESIGN TOKENS

Summary from the TLDR Design newsletter

Design token systems that work fine at 50 tokens often break at 500, typically because no one defined who owns changes, renames, or conflicting edits. Separating raw primitive values from semantic aliases lets a theme swap become a one-line change instead of a component-by-component hex-code audit, enforced with a simple linter rule. Treating renames as versioned, deprecation-windowed changes and generating every platform output from one source in CI, with a WCAG contrast check before shipping, keeps the system scalable.