Design systems sound like something only big companies need. But on three recent projects, a small one saved weeks of work and kept the product consistent as it grew. Here is what I learned building them.
Start from real screens
I never start a system with an empty Figma file. I design the first five or six real screens, then look for the pieces I keep repeating: buttons, inputs, cards, headings. Those become the first components.
Tokens before components
Colors, spacing, type sizes and corner radii go into tokens first. When the brand color changed halfway through one project, we updated one value instead of three hundred layers.
- Name tokens by purpose, like text-muted or surface, not by value, like grey-500.
- Keep the spacing scale small. Five or six steps is plenty.
- Match token names in Figma and in code, so designers and developers speak the same language.
Document decisions, not just pixels
A button component is useful. A note explaining when to use the primary button and when to use the secondary one is what keeps the product consistent when someone new joins the team.
A design system is a set of decisions you only want to make once.
Keep it alive
The system on my first project died because nobody owned it. On the next two, one designer and one developer reviewed changes every two weeks. That small ritual kept the library and the live product in sync.