Insights / UX Design

Design systems: copy the structure of the big ones, never their look

Before building our design system, we studied ten of the biggest. They all share the same structure. What to take from them, where their model stops for a small business website, and why the style sheets you find online are half wrong.

You don't need to build a design system from scratch. Take the structure of the big public systems, the ones from Google, IBM or GitHub, but never their look. At Pillet Grenié Bureau, we studied ten of them before building our own. They all share the same skeleton, so we took it as is. The more useful lesson was where that model stops.

Why borrow from the big design systems instead of reinventing everything

We read shadcn/ui, Vercel's Geist, IBM's Carbon, GitHub's Primer, Atlassian's system, Google's Material 3, and the systems behind Linear and ElevenLabs in detail. The material is free to read: most major design systems are open source, with a documentation site, design kits, tokens and large component libraries. Carbon, for example, focuses on accessibility and ships for React, Angular, Vue and Svelte. These systems hold years of decisions.

What struck us is that they all use the same architecture. You find principles and tokens, which are named base values for colours, sizes and spacing. Then come foundations, components, screen patterns and writing rules. Tokens sit on three levels: global, semantic and component. The payoff is practical. To add dark mode, you rewire a few names. Nobody repaints every screen.

They also share a closed vocabulary. Every name follows the same grammar (category, role, variant, state) and comes from a short list. That matters more than the syntax. Without the list, everyone on the project invents their own names, and you end up with a dozen button styles where four would do.

So we kept the role names from shadcn/ui, a widely used library. Each line pairs a role with a value:

:root {
  --background: #ffffff;
  --foreground: #111111;
  --primary: #1f4fd8;
  --border: #e4e4e7;
}

The names stay the same from one client to the next. Only the values change. Existing components plug in without edits, and AI tools understand what they read. A 2026 guide even recommends starting from a library with more than 20,000 stars on GitHub, because it gives those tools more context. This matters: a growing share of screens is generated by AI, and without a design system, each generation picks its own colours. Within weeks, the product drifts.

Our position is simple. Copy the structure, never the look. Your brand isn't Google's.

What Google, IBM and GitHub don't cover for a small business website

These systems are built for products: dashboards, forms, applications. They stop at components. A marketing website, though, is made of sections (a hero, services, case studies, testimonials, a call to action) and of pages that string those sections together with a certain rhythm.

In our reading, rules for sections only appeared in marketing systems, such as GitHub's Primer Brand or the ElevenLabs website. These keep marketing separate from the product, but they share a common base.

For a small business, missing this layer costs you quickly. The buttons are consistent, but every page is laid out differently. Every new page starts from a blank mockup. And the website and the app end up looking like two different companies.

So we added what was missing: a rhythm between sections, ready-made sections, page templates and written layout rules. Our catalogue holds more than a hundred section layouts. Each one describes structure and behaviour, never appearance. The style comes from the client's brand.

Documentation that no longer matches the code

The second limit is quieter. Every system whose reference documentation is written by hand has drifted away from its own code. In our own reading, we found a file meant for AI tools that still listed an old brand colour, and documentation that listed fewer colour themes than the code actually produced.

The cause is mundane. A value gets copied to five places, then updated in only one. For you, the result is a new page that sits slightly off-brand, and nobody knows why.

Copying a brand's style from the internet is a risky shortcut

Style sheets circulate online. They claim to describe the brand of Linear, Vercel or ElevenLabs, ready to hand to an AI tool. We checked three of them, value by value, against the real websites.

For ElevenLabs, about half the values were wrong: a grey background instead of off-white, a brown button instead of black, a headline larger than it really is. The sheet also listed five pastel colours that don't exist in the site's code, because they're images.

For Linear, the colours were nearly right. But the font names were made up, the buttons were described as square when they're rounded, and the sheet claimed there's no light theme. There is one. For Vercel, what the sheet said about the licence of the Geist fonts didn't match what we found when we checked. A mistake like that could make you pass on a font you're free to use, so always check a licence at the source.

These sheets are written by people looking at the website, not exported from the brand's own sources. They fill the gaps with plausible guesses, and nobody checks or updates them.

Our rule: a sheet you find online can point you in a direction. It should never set your values. When we need the real values from a reference site, we read them straight from the browser. We start with five points: background, text colour, font, headline size and button corner radius. It takes a few minutes.

How we build a client's design system without starting over

The decision is always the same. We start from a fixed skeleton shared by all our projects, then add a short brand sheet for each client: text and background colours, accent, fonts, shapes, motion and the default layout for each section. The website, and later the app if one comes, start from the same base.

We begin with an inventory of what already exists, as Figma's guide recommends. That guide also offers a handy rule of thumb for colour: roughly 60% neutrals, 30% primary colour and 10% accent.

The safeguard is that values live in one place only. The documentation, the website styles and the file AI tools read are all generated from that single source. Hand-written text contains only rules and refers to tokens by name, never copying their values. A check blocks the release as soon as a copy falls out of date. We applied it to our own website first.

The cost is measured in time, and it stays predictable. Putting a new brand on the skeleton takes minutes. Tuning the tokens takes hours. Building sections specific to the project takes days. A French studio confirms that a palette, a type scale and a spacing grid can be set up in a few days, along with five first components: button, input, card, modal and table.

What you get is a website and a tool that speak the same language, AI-generated screens that stay on-brand, and documentation you can trust. If you're planning a website or a custom tool, this is the foundation Bureau lays in its build projects.

Written by

Pillet Grenié BUREAU was founded by Quentin Pillet and Tom Grenié.

About the studio
Related service

Product build

Design and build a web product, internal tool or client portal—or help finish a project that has stalled.

More on UX Design

Tell us what you need help with.

You don’t need a finished brief. Tell us what you’re trying to do, what is getting in the way and what you’ve already tried.

Start a conversation
Technical Insight