A design system starts with foundations, not components: color, typography, spacing, radius and duration tokens, then about a dozen components that cover most screens, named the same way in Figma and in code. Documentation and governance come next, built from real screens.
Before you start: three questions
- Who will keep it alive? A system with no named owner dies within six months. Name someone, even at 20% of their time.
- For which team? A system for four people has nothing in common with a system for forty. Size it accordingly.
- What product already exists? A system is not built in a vacuum. It starts from an inventory of real screens.
Step 1: the inventory
Before designing a single token, take stock of what exists. Capture every button, every input, every color and every text size used in the product. You will probably find four primary buttons, eleven grays and seven body text sizes.
This inventory serves two purposes: it shows decision-makers the size of the problem, and it gives you the list of components you actually need.
Step 2: tokens
Tokens are the smallest and most stable design decisions. I set them in this order.
| Family | Content | Advice |
|---|---|---|
| Primitive color | The raw palette: grays, accent, states | Few hues, a regular scale |
| Semantic color | Background, surface, text, accent, success, error, warning | Components use these, never the primitives |
| Typography | Families, fluid scale, weights, line heights | A scale of six to eight sizes is enough |
| Spacing | A 4 or 8 pixel scale | Every margin and padding derives from it |
| Radius, shadows, borders | Three radii, three shadows, two borders | Beyond that, nobody knows which one to pick |
| Motion | Three durations, two easing curves | Motion is a system decision |
Semantic tokens are what make dark mode, white labeling or a brand refresh possible without touching the components.
Step 3: the first twelve components
Build them in order of use, each with its variants and states (default, hover, focus, active, disabled, error, loading):
- Button
- Input
- Select
- Checkbox and toggle
- Table
- Card
- Navigation
- Tabs
- Modal
- Notification
- Badge
- Avatar
Resist the temptation to do more. A component joins the system when a need comes up a second time.
Step 4: Figma and code, same names
The gap between the Figma file and the code kills most systems. Agree on a single naming convention and apply it on both sides:
- Figma variable
color/surface/raisedequals CSS property--color-surface-raised. - Figma component
Buttonwith atoneproperty equals component<Button tone="…">. - Text style
text/body/mdequals tokentext-body-md.
If the team uses Code Connect or a token layer exported as JSON, automate the link. Otherwise, document it and check it at every review. The topic is covered on the front-end development page.
Step 5: minimal documentation
One page per component, four sections:
- When to use it.
- When not to use it, and what to use instead.
- An example taken from the product.
- A counter-example taken from the product.
That's it. Documentation is written from real screens, after use. Writing documentation before anyone has used the component produces pages nobody reads.
Step 6: governance
Three rules are enough at the start:
- A single channel for component requests and inconsistency reports.
- One owner who arbitrates and publishes releases.
- An exception rule: a deviation is allowed if it is tracked; if it comes up twice, it becomes a component.
The five most expensive mistakes
- Starting with components: everything has to be redone at the first brand change.
- Copying a big system (Material, Carbon): it solves other people's problems, not yours.
- Trying to cover every case: the system covers the frequent cases and tolerates exceptions.
- Documenting before using: documentation serves people who already have the need.
- Not naming an owner: see question number one.
A real example
On Climeet, the Figma system was set up in three weeks from the wireframes: tokens, typography, about fifteen components. When the client asked for a simplified version of the calculator, the foundations did not move. Only the screens changed. The same system then powered the marketing website. That is exactly what a design system should make possible.
For hands-on support, see the design system page.

