Correct by Design · Design systems for AI agents

Why this matters

Your design system's biggest user is no longer a person.

Whoever's driving, designer, engineer or product manager, more of your UI ships from an agent every month. It never opens your design file. It reads your repository.

If your system isn't 100% legible there, the agent doesn't follow it. It improvises, confidently, at speed, in code that looks fine in review.

UI nobody designed, from more directions every month. Either review becomes the bottleneck, or the wrong thing ships.

The approach

The design system is infrastructure.

Design lives in the code, not downstream of it.
Wrong output is impossible, not discouraged.
The agent is the primary user.
Everything is measured, never asserted.

How the work is done →

The standard

A design system built to these principles.

Not a slide about the principles above. A complete design system that holds to them: tokens defined once, components where the wrong build will not compile, documentation an agent reads without leaving the repository.

Then a coding agent built a working application from it, with no design direction. The result is the system's output rather than a designer's, which is the whole claim made concrete.

It's available to look through on request. Worth a look before you commit to anything. Request the sample →

The audit

Three parts, one document.

OneI count what's actually in your codebase. Hard numbers, with file references, not an opinion about your design system.
TwoI make an agent build with it, and you watch. Before it runs, I tell you what I expect it to get wrong.
ThreeI separate the three kinds of failure: what your docs didn't say, what your components allowed, and what doesn't exist in your system at all.

What part one counted at Nivoda, a global B2B marketplace running Material UI:

81per-component override files fighting Material's defaults

723inline style escapes, every one a place a token could be ignored

32component-specific token files maintained by hand

What those numbers led to →

Correct the system, not each output

Your design system's biggest user is no longer a person.

The design system is infrastructure.

A design system built to these principles.

Three parts, one document.

Start with the audit.