Design systems have no rule book that agents can obey.
An agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. has no tacit knowledgeWhat a team knows but never wrote down.. It reads what is written and obeys what is enforced. No framework says which rule wins, how strict each rule is, or what proves that a rule holds.
Pavol Hudran. I have built design systems since 2011. This site is what I learned, with the evidence.
Read the white paper Find your level Slides, TechMeetup 2026
Where this is heading.
A design system is becoming the contract an agent works under. The parts already exist: a rules file, tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format. with a resolverThe part of a token set that selects the values for a context, for example a brand or a mode., a component registryA list of the components of a system that a tool or an agent can read. and an open protocol for agents. What is still missing is a shared rule book: which rule wins and which check proves it. Read the white paper
- 1Decisionsa person decides
- 2Tokensa build turns them into code
- 3Componentsowned code, a registry
- 4Rules for agentsAGENTS.md and skills
- 7Proposalsa person approves
- 6ChecksCI judges, byte for byte
- 5Agentsselect and fill
- a person
- a build
- a file
- an agent
- a check
Fifteen years, five of my design systems: where the decision was buried, and where it moved.
Each time, I did one thing: I took a decisionA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register. out of where it was buried and put it where the next reader could use it. In 2026, the next reader is an agent.
The same, as a table
| Era | Buried in | Moved to | Read by |
|---|---|---|---|
| 2011 · Makro, M-Objednávka | one project's skin | a method, several build targets | several teams |
| 2015 to 2016 · ČP Invest, Generali Investments | a CSS framework's compiled output | variables and a skin layer | one team |
| 2022 to 2024 · Notino | design files and designers' heads | tokens as data, versioned packages | 15 internal teams |
| 2026 · rules for agents | people's tacit knowledge | numbered decisions, each with a named check | AI agents |
MCPModel Context Protocol. The open protocol that agents use to read tools and data. tells an agent what exists. It does not say how the team uses it, which rule wins a conflict, or whether the result is correct. That layer is open. The white paper describes what it needs.
An agent has no tacit knowledge.
It reads what is written and obeys what is enforced.
An agent has no tacit knowledge.
It reads what is written and obeys what is enforced.
Only the reader changed.
This site shows the same move, live.
One token set. One resolver with two modifiersA named choice in the resolver with its options. This site has two modifiers: brand and mode., brand and mode. Four permutationsOne combination of the modifier options. This site has four., no component changes. Drag the seam, or add ?brand=kiln to any address.
Five levels. Each answers one question about a decision.
Levels 1 and 2 are not obsolete. Weak tokens give an agent nothing solid to select from. The step from 3 to 4 is not a purchase. It is a list of decisions, an order of authority and checks.
Four steps to start this week.
For you, if you run a design system and want coding agents to follow it. These are not prompts. They are four changes to your own repository, small enough to start this week.
- Spend one hour counting what your system has against the Design System Checklist.
- Write a short rules file that names what the agent gets wrong, with the correct replacement.
- Number your decisions and add an "Enforced byThe field of a decision that names the check that proves it, or says "not enforced (gap)"." column. Leave it honestly empty where nothing checks the rule.
- Add one check that runs in CIContinuous integration: the checks that run on each change of the code. for the rule that hurts most.
This site is built by the method it describes. Check it.
- Same code, two brands. Press the switch in the header. Components do not change; only
data-themedoes. - The register, in public. Every rule names its check, or says
not enforced (gap). All decisions - Every number is on record. Each figure on this site is an entry in a public registry, with its base, source and date. The claims registry
A brand voice guide your tooling can prove.
Voice and Tone is my open-source plugin for Claude. It turns a vague voice guide ("warm, but professional") into rules an agent can follow and a reviewer can check. Every rule records where it came from and how sure it is. Tone is computed from 80 tone cells from 18 stored rows.
It is built on Mailchimp's Voice and Tone framework, not on a design system. What it shares with this site is the method: evidence before authority, and checks in code.