r/DesignSystems • • 5h ago

We rebuilt our design system so our team and AI agents follow the same rules and get the same UI

Post image
15 Upvotes

Our team (one designer, one engineer) spent 3 weeks rebuilding our design system, MBSW, around one question: can a human and an AI agent start from the same source and end up with the same UI?

When we asked AI to follow our old system, it kept rebuilding components we already had and picking colors that were only close. The rules it needed lived only in someone's head, not anywhere it could read.

What we changed:

  1. Two layers per component. An intent doc (MD) written by the team explains when and why to use it. The values (JSON) are generated by a script from a Figma version the design team has approved.
  2. No AI summarizing Figma. We first had AI read Figma through MCP and turn it into JSON, but the same component came out slightly different every run. Pinning the Figma version and using the REST API made the output identical, whoever runs it.
  3. Tokens mapped by intent, not by value. Different tokens can share the same color, so the value alone can't tell you which token it is. We map values through Figma variables and keep each confirmed mapping.
  4. No filling gaps by guessing. If we've agreed on a behavior that isn't drawn in Figma, it goes in the intent doc. If a token mapping is missing or ambiguous, the AI doesn't pick one just because the name or color looks close; it waits until we confirm.

It's public (React 19, MIT) if you want to see how the docs and tokens are structured: https://rdo.sh/G1SCiIV

Curious how other teams approach this. Do you write documentation with AI as a reader in mind, and what has worked or not?


r/DesignSystems • • 4h ago

How are you handling AI agents in your Figma workflow? I built a local bridge and want honest feedback

Thumbnail
reddit.com
1 Upvotes

r/DesignSystems • • 5h ago

Are others using more than one design system for their company?

1 Upvotes

Is it overkill to create an entirely separate design system for my marketing site and ad content?

My SaaS app is one thing but the marketing site is starting to take a very different turn and making one design system was starting to get more complicated to accommodate both.

I'm on the track that I'm about to create a second one but now I'm going to have a lot of duplicate tokens such as colors for example.

Has anyone else faced this issue and do you have any suggestions?


r/DesignSystems • • 17h ago

A design-system gate caught 46 color violations, then exposed the palette I did not have

1 Upvotes

I added a deterministic “steel curtain” to my portfolio repo. It checks only the lines a pull request adds and blocks things it can prove are wrong: raw colors that already have tokens, classes with no stylesheet, images without alt text, and a few other mechanical rules.

On my homepage redesign it finished in 38 seconds and stopped the merge on 46 findings. Every blocker was a color I had already named. Twenty-nine were exact token values typed by hand, and 14 of those were inside one sticker component.

The report-only findings were more interesting. Thirteen colors were too far from any token to block. Ten of the twelve unique colors were drawing materials: sticker release paper, aluminum, glass, a bezel, and a lens.

My system has a brand palette. It does not have a material palette.

The gate also writes proposed components and patterns into a registry for me to review. It has proposed 18 additions so far. I have promoted none. The script can spot drift and collect evidence; deciding what the system should keep is still manual.

I am trying to decide what the correct layer is for those material colors. Would you:

  • promote them into the main token system;
  • create a separate material palette with its own rules;
  • keep them local to the illustrated objects;
  • or treat this as evidence that the gate is checking at the wrong level?

Full write-up with the receipt and swatches:

https://www.rdeboerdesigns.com/notes/the-gate-stopped-my-redesign/