Your agents aren't following your design system
Agents can know every rule in your design system and still break them. Knowing a rule is not following it, and enforcement is what holds the standard.
Coding agents can know a design system’s rules before I type a word. Rules files and project instructions load at the start of every session. Even so, building four products at Craftform over the past few months, I corrected the same mistakes dozens of times: the wrong border, a colour in the wrong place, a card with a coloured stripe down its left edge.
The usual answer is “we have a design system.” It doesn’t solve this, because knowing a rule and following it are different things.
Written for people
A design system is written for people. A designer reads it once, absorbs the intent, asks when something is unclear and remembers what matters most. An agent does none of that. It weighs everything unevenly, and the longer the document, the more often rule forty loses to whatever the model would have done anyway. Agents sometimes ignore a one-line instruction given in the same conversation. A hundred pages has little chance.
Fewer rules, enforced
So I cut my rules down to a short list, each one a correction I had made more than twice:
- Every tile surface gets a half-pixel border at 6% black.
- No monospace type anywhere in the app interface.
- Never use a left border for emphasis.
- In Restform, amber means training and blue means journal, everywhere.
- Journal prompts are always phrased as questions.
- The iOS app never sends you to the website to change a setting.
Vague rules like “make it feel premium” did nothing. Specific ones, especially those phrased as “never”, did better, because a machine can check them. They still didn’t hold on their own. No left borders is the rule I had written most clearly, and it was the one agents broke most.
What made the difference was enforcement, which is why I built Liveform. It learns from the corrections I make, reviews everything an agent builds against those rules and sends problems back to the agent to fix. The left borders stopped reaching me. My job moved from reviewing to spotting what no rule covers yet, and naming it precisely enough to add.
What this means for design leaders
-
A design system is not proof of quality. Judge what ships, not what is documented.
-
Give it a second form. Alongside the documentation for people, keep a short set of specific rules that can be checked automatically.
-
Own the enforcement. At agent volume, review can’t happen in crits. It has to be built into the process, and if design doesn’t own it, engineering will build it to its own priorities.
A design system tells people what good looks like. Agents need something that holds them to it.