Skip to content
FREN Book a call
( Design Systems )( 03 / 10 )

Design system

A design system is not a component library: it is a shared language between design and engineering. I build it at the scale of your team, not at the scale of a tech giant.

Design system

( Key facts )

Who
Vladimir Spalaikovitch (Vladispala), senior freelance UX/UI designer based in Paris, 20 years of experience
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
Tools
Figma, Code Connect, CSS, JSON
Contact
A 30-minute call booked online or contact@vladispala.fr, reply within one business day

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: 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: 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: 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.

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.

( FAQ · 05 )

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.

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.

( Next · 05 )

Keep reading

  1. Design system: where to start when you are starting from zero

    How to start a design system: the right order for foundations (tokens, type, spacing), the first twelve components, Figma and code, minimal documentation.Starting a design system: foundations, first components, Figma and code. · 3 minRead
  2. UI design and product design

    Senior freelance product designer and UI designer: premium interfaces end to end, Figma screens with every state, components, clean handoff. Book a call.Senior product designer and UI designer: premium interfaces, from Figma to handoff.UI · Product DesignRead
  3. Front-end development: a designer who codes

    UX/UI designer who codes: realistic prototypes, pixel-perfect HTML, CSS and React front-end development, fast static websites and hands-on developer support.UX/UI designer who codes: realistic prototypes and HTML, CSS and React builds.Design · DevRead
  4. Climeet

    Climeet case study: art direction, a Figma design system and React prototyping for an app that measures the carbon footprint of events, plus its website.Art direction, design system and React prototype for a carbon footprint app.Event tech · Carbon · Design systemRead
  5. HyperDrive for Galaxy

    HyperDrive case study for Galaxy Semiconductor Intelligence: UX/UI design of a semiconductor analytics platform: ML rules, statistical limits, simulator.UX/UI design of a semiconductor production analytics platform.Industry · Data · SemiconductorsRead