Make.com Design System

Took Make’s design system from Angular-only to framework-agnostic and agent-ready.

4 min read

Design system components and color tokens for Make.com

Make’s design system used to work only in Angular, and most designers didn’t use it at all. Today it works in any framework, ships with its own MCP server and agent skills, and Figma counts around 16,000 to 18,000 component inserts a month. My job changed along the way. I started as the designer next to three developers; now I own the system’s whole frontend, from component specs and tokens to component code, Storybook pages, guidelines and the Figma libraries.

Client
Make
Role
Design Lead
Team
3 Devs
Timeline
2024 – Today

01

Three versions

  1. Before me

    Version 1

    Angular only. Designers barely used it in Figma.

  2. 2024

    Version 2

    My first rebuild, with little developer support.

  3. 2026, now

    Version 3

    Framework-agnostic and agent-ready.

Version 1 was built only for Angular, and I didn’t build it. Designers barely used its tokens or components in Figma, because creating anything with them took ages. The visual style was outdated and no longer matched where Make was going.

Version 2 was my rebuild, starting in 2024. I’d never worked on a design system before, we had little developer support, and I made a lot of mistakes. Our first token idea grouped everything into interactive and static. It looked simple, but people didn’t understand it. The names didn’t survive code either: nobody could read the CSS classes back.

02

The turn

At the start of 2026 two new developers joined. Now it’s me and three developers: one looks after the old Angular system, two build everything new, and one of those two is also a bit of a PM for us. Since then we’ve shipped more than in the two years before: agent skills, our own MCP server, platform-wide dark mode, and the framework-agnostic system under all of it.

The framework-agnostic move itself wasn’t the hard part. My developers made it easy from where I sat, and I learned a lot from them doing it. A shared styles layer now carries every visual decision, so a change shows up the same way in React, Angular or Svelte.

The styles layer behind the Button: fill, label, height, padding, gap, radius and focus each bound to a token
React, Angular and a Web Component rendering the same dom-button markup, styled by one button.css

03

Fewer tokens, plainer names

We dropped the interactive and static grouping, cut the semantic tokens from 430 to about 160, and renamed them so people can read them.

Version 2
background/interactive/brand/defaultCSS class: dmo-bainbr-default
Version 3
surface/brand/default

Renaming every token breaks every consumer, so we split the change in two. First we gave the version 2 tokens their version 3 values, in code and in Figma. That shipped the new visuals without anyone changing a line of product code. Now we’re doing the actual replacement, with our MCP server and bots helping developers swap the names. We ran internal interviews before each change, which kept the risk low.

The hard part is the mapping. The product carries two versions of the old system plus custom CSS, and all of it has to land on the new tokens.

A cross-section of the 428 version 2 colour tokens, long names such as Background/Interactive/Brand/Default
Version 3 colour tokens with plain names, grouped as surface, type, icon, outline and overlay

04

Two products, one palette

Make has its main product and Make Grid, a layer above it that shows your organisation as a 3D isometric canvas, so you can see how your automations connect. Grid was visually more advanced, and we wanted the two to feel like one product.

We adopted Grid’s colour palette, but the semantic token values took arguing. The main product uses saturated colours; Grid uses pastels. We found the common ground through close work between me, Grid’s designer and our developers.

Saturated and soft colour scales side by side, with the semantic tokens that draw from each

05

How I work now

I work mostly in Cursor and Claude Code, with Figma for visual work and the designers’ libraries. I’ve written my own skills, each with its own rules, and set up bots around them:

Specs
A skill interviews me about a spec before a component is built.
Docs
Skills write the Storybook documentation, guidelines and component specs.
Figma
A skill uses the Figma Console MCP to build the component in a set format: the component, its anatomy documentation, and a header linking to Storybook.
Consistency
A Grok bot checks code against Figma and flags any nuances for me.
Feedback
Another Grok bot watches our Slack feedback channel and turns feedback into tickets.
The component skills in order, from plan-component to create-pr, beside the Domino MCP endpoints and tools agents use

Next we’re building a pipeline of Grok bots that also propose the fix and open a pull request for us to review. We need to polish the flow and the components first.

What I still do by hand is review: in Figma and Storybook I check how tokens and components actually look, whether they stay consistent across the system, and whether their properties make sense. Our developers’ AI setup is more sophisticated than mine.

06

The knowledge hub

The part I’m proudest of is the Obsidian knowledge hub my agents read from. It holds everything about the system: Figma and code, the skills, the changelog, my ideas. When developers comment on my pull requests, those comments are recorded there, so the agents get it right next time instead of repeating the mistake. I also log ideas about components as they come. When I later work on that component, the agent pings me: you had an idea for this.

The Obsidian graph of the Domino vault: Domino3 at the centre, review and decision notes, and a cluster of logged component ideas

07

Impact

Component inserts a month in Figma, 2026
16,000–18,000
From 800–1,000 on the old system
Dark mode to production
4–5 weeks
The first draft took six months on the old system
Semantic tokens
~160
Down from 430
Detach rate
~5%

The six months were largely technical debt. On the new system, dark mode was tested with users and internally before it shipped. Insert and detach figures come from Figma library analytics. A new version is coming soon.

08

What I believe now

Setting up a design system is tough, with a lot of hiccups along the way. It’s 100% worth it, especially now that agents build alongside us.

The hiccups are worst on a platform with a lot of legacy code. I always knew a design system mattered. What I didn’t know was how complex one can get while staying easy to use. Version 2 was my first design system, and I learned a lot along the way from my developers.

Next case studies

Interested in working together? I’d love to hear about your project or team.