For years a design system had one kind of reader: a designer, a developer, a new hire in their first week. Today the reader who opens it most is a model. It reads every rule, every time, and it does exactly what the words say.
That changes what a good rule is. “Keep it clean” worked when a person filled the gap with judgment. A model fills the gap with the average of everything it has seen, and the average is the page every startup already has.
A rule you can break on purpose
So we write the system as a specification. Every rule has to be breakable in a way you can see. “Body text at 4.5:1 against the surface it sits on” can be measured. “Elegant” cannot. If nobody can tell whether a rule was followed, it is decoration, and it goes.
| Taste | Spec |
|---|---|
| Feels premium | Display face Bodoni Moda, 500 or 600. Never bold. |
| Use the brand purple | #390787 is light, never text, on a dark ground. It measures 1.42:1. |
| Keep it clean | No card grids. No stat tiles. One display weight per screen. |
| Make it accessible | Body text at 4.5:1 or better against the ground it sits on. Checked, not assumed. |
The reason travels with the rule
Our purple carries no text on a dark ground because it measures 1.42:1 there. The number is the reason, and it sits next to the rule. A model that knows why can handle the case the rule didn’t name. A person who disagrees has something real to argue with.
Models are good at adding. The system’s job is to subtract.
So the system says what is forbidden as clearly as what is allowed. No card grids. No stat tiles. One display weight per screen. Every line of “don’t” saves a review.
Smaller than the work
A system a model can hold in one read beats a site of components nobody opens. Tokens first, then rules, then the few pieces we actually reuse. Each project still owns its look. The system only says what may not change.
Taste does not disappear. It moves upstream. You decide what is true, write it down, and check the output against it. The designer becomes the editor.



