Foundations for Design Systems
Design system foundations start with an audit of the existing interface to find duplicated colours, spacing values and components, then set principles for what the system should achieve. The core building block is the design token, a named value such as color-text-primary that stores a design decision once and is reused everywhere.
Stage: Foundations · Part of the Design System roadmap · Last reviewed 19 November 2026
What to learn in Foundations
- Run an interface inventory and group near-duplicate styles
- Write design principles that help choose between options
- Define primitive and semantic design tokens with clear names
- Store tokens in JSON and export them as CSS variables
- Decide a naming convention for colour, spacing and type scales
- Explain the difference between a token and a raw value
Foundations interview questions
What is the difference between primitive and semantic tokens?
Primitive tokens hold raw values, such as blue-500 equals a hex colour. Semantic tokens name a purpose, such as color-action-primary, and point to a primitive. Components use semantic tokens, so you can rebrand or add a theme by changing the mapping only.
Why start with an audit?
An audit shows the real state: how many shades of grey, button styles and spacing values exist. It gives evidence for consolidation, finds the components worth standardising first and avoids designing a system that ignores what products already need.
Where Foundations fits in the Design System roadmap
Foundations belongs to the Foundations stage (beginner level), which takes about 18 hours. Principles and tokens.
Other units in this stage
Back to the full Design System roadmap