The design system becomes the contract an agent works under
This is where I think design systems go, and why. I mark each judgment as a judgment.
For fifteen years a design system was written for people: a library, a guide and a few experts who knew the rest. AgentsAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. now write a large part of the interface, and an agent has no tacit knowledgeWhat a team knows but never wrote down.. It reads what is written and obeys what is enforced.
So the system has to change shape. It stops being documentation and becomes a contract: decisionsA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register. with reasons, tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format. as data, components as code, rules an agent can read and checks that prove the result. The parts already exist. Few teams have joined them.
Five shifts, already under way
- 1Rulesa wiki page people readAGENTS.mdA file in a repository with the instructions for agents. next to the codeopen format
- 2Tokensone theme file per brandone source and a resolverThe part of a token set that selects the values for a context, for example a brand or a mode.stable spec
- 3Componentsa package to importa registryA list of the components of a system that a tool or an agent can read. an agent searchesshipping
- 4Design filesread by agentswritten by agents toobeta
- 5Design toolsa separate appinside the conversationmoving
1. Rules move into the repository. A short rules file next to the code tells an agent what goes wrong and what to do instead. The format is shared now: AGENTS.md and MCPModel Context Protocol. The open protocol that agents use to read tools and data. moved to the Agentic AI Foundation under the Linux Foundation on 9 December 2025. It works: in one test of the Supernova tool, a 12-line rules file removed every rule break.
2. Tokens become one source with contexts. Brand, mode and density stop being copies of a theme. The DTCGThe Design Tokens Community Group and its file format for design tokens, version 2025.10. A Final Community Group Report, not a W3C standard. Resolver Module 2025.10 combines token sets through modifiersA named choice in the resolver with its options. This site has two modifiers: brand and mode. such as light and dark. This site runs on one resolver with two modifiers, brand and mode.
3. Components ship as registries an agent can search. An agent installs owned code from a registry instead of guessing an import. The shadcn MCP server works with any registry that follows the shadcn registry specification.
4. Design files open in both directions. Agents can write to the Figma canvas through Figma's MCP server, using the team's components and variables. The design tool becomes one more client of the system, not its only home.
5. Design tools move into the conversation. Claude Design is moving into Claude: a research preview in April 2026, inside every Claude conversation since September, the standalone site closing on 14 December. Its own working rule is the one this site follows: code is the truth, screenshots are lossy.
How it should work
One loop, from a decision to a check and back. Every step is a file in the repository, so a person and an agent read the same facts.
- 1Decisionsa person decides
- 2Tokensa build turns them into code
- 3Componentsowned code, a registry
- 4Rules for agentsAGENTS.md and skills
- 5Agentsselect and fill
- 6ChecksCI judges, byte for byte
- 7Proposalsa person approves
- a person
- a build
- a file
- an agent
- a check
- Decisions. Numbered, each with its reason, the option rejected and the check that enforces it. Where nothing checks a rule, the register says so.
- Tokens. DTCG files and one resolver. A build turns them into code; nobody edits the output by hand.
- Components. Owned code that reads tokens only, published as a registry.
- Rules for agents. A short
AGENTS.mdthat names what goes wrong, with the correct replacement. SkillsA file that tells an agent how to do one task. In my method, a skill applies a rule. It does not make one. apply the rules; they never make them. - Agents. They read all of the above through MCP. They select and fill. They do not invent a colour, a spacing value or a component.
- Checks. DeterministicGives the same result each time, with no language model. scripts in CIContinuous integration: the checks that run on each change of the code. judge the result: the same input gives the same verdict, byte for byte. A failed check names the rule it protects.
- Proposals. When an agent meets a gap, it writes a proposal instead of a new rule. A person approves it, and it becomes a numbered decision. The loop starts again.
This is the ladder from level 3 to level 5. Find your level
What I expect
These are bets, not facts. I will check them against this page in a year.
- Judgment: the main output of a design-system team becomes the decision register and its checks. The component library stays, but it is no longer the product.
- Judgment: open files win the format question. Tokens in DTCG, rules in
AGENTS.md, components in a registry. The lock-in moves to the checks a vendor runs for you. - Judgment: design tools and coding agents meet on the same protocol. A designer's change and an agent's change pass the same checks.
- Judgment: self-maintaining systems stay mostly demo through 2027. Agents propose; people approve.
What is still missing
The industry has the parts, not the trust.
- developers use AI to write code68%
- designers and developers trust the output32%
- practitioners see UI that bypasses the system59%
68% of developers use AI to write code, but only 32% of designers and developers trust the output. In another survey, 59% of practitioners report UI that bypasses the design system.
No tool I reviewed stores a team's usage rules with an id, a severity and a link to the check that enforces it. That layer is open. This site is one working version of it, with its own gaps in public.