Explain token aliasing in design systems

WHAT THIS TESTS This question probes whether you understand the indirection that makes design tokens scalable, and whether you can articulate the separation between a raw value and its intended meaning.

A GOOD ANSWER COVERS Describe three tiers. Primitive tokens are the raw palette, like blue-500 or space-4, with no meaning attached. Semantic tokens alias primitives by intent, like color-background-button-primary pointing at blue-500. Component or scoped tokens may alias semantic ones further. Components reference only semantic tokens, never primitives. The advantage for theming is that a dark theme or alternate brand simply repoints semantic aliases to different primitives without touching component code. The advantage for maintenance is a single source of truth: changing the brand blue updates one primitive and cascades everywhere, while intent stays stable.

COMMON WRONG ANSWERS Saying aliasing is just a naming convention, or that a flat token list is equally good. Claiming components should reference primitives directly. Forgetting that the whole point is decoupling value from meaning so themes can swap values safely.

LIKELY FOLLOW-UPS How do you prevent semantic-token explosion? How do you handle a one-off color that has no semantic meaning yet? How does this interact with light, dark, and high-contrast themes? What tooling generates platform outputs, such as Style Dictionary?

ONE CONCRETE EXAMPLE A primary button uses color-background-button-primary. In the default theme that semantic token aliases blue-500. For a dark theme you redefine the same semantic token to alias blue-400 for better contrast. The button component never changes; only the alias mapping does, and every primary button across the product updates consistently.