# Design system

> Design system design: tokens, Figma and code components, documentation and governance, for teams that want to ship faster and stay consistent. Let's talk.

- URL: https://vladispala.fr/en/expertise/design-system/
- Author: Vladimir Spalaikovitch (Vladispala), Senior UX/UI Designer, Product Designer and Digital Art Director, Paris
- Updated: 2026-10-04
- Version française: https://vladispala.fr/expertises/design-system/

## Key facts

- **Who** : Vladimir Spalaikovitch (Vladispala), senior freelance UX/UI designer based in Paris, 20 years of experience
- **What** : Design system design
- **For** : Product teams that want to ship faster and stay consistent, at their own scale
- **Format** : Audit, foundations or ongoing support · 3 to 6 weeks for the foundations
- **Deliverables** : Tokens, components, documentation, governance

A design system is a set of reusable design decisions: tokens (colors, typography, spacing), components with their variants and states, usage rules and documentation, shared between designers and developers. It helps teams ship faster, more consistently and more accessibly.

## What I build

I size the system to the team that will keep it alive. A system too ambitious for a team of four ends up abandoned. A system too light for a team of forty fragments.

### Foundations

- **Tokens**: semantic colors (background, surface, text, accent, status), fluid type scale, spacing scale, radii, shadows, animation durations.
- **Themes**: light and dark, plus white label when the product is resold to clients who want their own identity.
- **Grid and layout**: containers, columns, breakpoints, density rules.

### Components

A dozen components cover 80% of a SaaS product's screens: button, field, select, checkbox, switch, table, card, navigation, tabs, modal, notification, badge. Each ships with its variants, its states (default, hover, focus, active, disabled, error, loading) and its accessibility rules.

### Documentation and governance

- One page per component: when to use it, when not to, examples, counter-examples.
- A contribution process: who proposes, who approves, how an exception becomes a component.
- A changelog the whole team can read.

## Figma and code, one language

Most systems break at the gap between the Figma file and the code. I close it at the source:

| In Figma | In code | Why |
|---|---|---|
| Color variables `color/surface/raised` | CSS property `--color-surface-raised` | Same name, no mental translation |
| `Button` component with a `tone` property | `<Button tone="primary">` component | Variants map to props |
| Text styles `text/body/md` | Class or token `text-body-md` | One single type scale |
| Light / dark mode | `data-theme` attribute | The theme is data, not duplication |

When the team wants it, I write the Code Connect files or the token layer (JSON, CSS) so the link is tooled rather than just documented.

## Real cases

- **[Climeet](https://vladispala.fr/en/work/climeet/)**: a full Figma design system for a carbon footprint app, with tokens, components, variants and a library reused on the marketing site. The system made it possible to rebuild the calculator as a simplified version without redrawing the foundations.
- **[Reformer Society](https://vladispala.fr/en/work/reformer-society/)**: a dark system with white label per studio, an accent color overridden by each client, the same components across three areas (public, studio, super admin).
- **[WeeFizz](https://vladispala.fr/en/work/weefizz/)**: design system for the PRO SaaS and the e-commerce widget, with an i18n system in eleven namespaces and components shared across four CMS integrations.

## Mistakes I avoid

1. **Starting with components** instead of tokens: everything has to be redone at the first rebrand.
2. **Copying a big player's system**: it solves their problems, not yours.
3. **Documenting before using**: documentation is written from real screens.
4. **Trying to cover every case**: a system covers the frequent cases and allows tracked exceptions.

The full method for getting started is in [Design system: where to start](https://vladispala.fr/en/blog/design-system-where-to-start/).

## Engagement formats

- **Audit of what exists** (one to two weeks): inventory of real components, Figma/code gaps, consolidation plan.
- **Foundations** (three to six weeks): tokens, core components, initial documentation, handover.
- **Ongoing support** (a few days a month): contribution reviews, trade-offs, system evolution.

[Let's talk about your system](https://vladispala.fr/en/contact/).

## Frequently asked questions

### At what team size does a design system make sense?

As soon as two people produce screens, or the product has more than a dozen screens. Before that, a clean stylesheet and well-named Figma components are enough. The system becomes essential when consistency starts costing time every sprint.

### How long does it take to set up a design system?

The foundations (tokens, typography, colors, spacing, a dozen core components) take three to six weeks. The rest is built as real screens come in. A finished system does not exist: it lives with the product.

### Is Figma enough, or do you need code too?

The two must match, otherwise the system only serves designers. I name components and tokens the same way in Figma and in code, and I work with developers so the component library mirrors the Figma file. See [front-end and design](https://vladispala.fr/en/expertise/front-end-development/).

### How do you keep a design system from going unused?

Three levers: short documentation with usage examples, a single channel for component requests, and a named owner. A system nobody owns dies within six months.

### Design system design with Vladispala: what format, how long, which deliverables?

Design system design with Vladimir Spalaikovitch (Vladispala). Format: audit, foundations or ongoing support. Duration: 3 to 6 weeks for the foundations. Deliverables: tokens, components, documentation, governance. He works from Paris, on site in the Île-de-France region and remotely everywhere else, in French and English. The first step is a 30-minute call booked online.


---

Contact: https://calendar.app.google/1nHYAgzZcMcMqCbV7 · contact@vladispala.fr · https://www.linkedin.com/in/vladispala/
