Five levels. Each answers one question about a decision.
I use this ladder to find where a design system stands and what to do next. Six questions, nothing is stored.
A level says where a design 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. lives and who can use it. It is not a score. A system can be strong on level 2 and absent on level 4.
| Level | Name | The decision is… | State of the industry, 2026 |
|---|---|---|---|
| 1 | Themable code | separated from structure | Solved. CSS custom properties are baseline |
| 2 | Token pipeline | data, versioned and deployed | Standard. DTCGThe Design Tokens Community Group and its file format for design tokens, version 2025.10. A Final Community Group Report, not a W3C standard. 2025.10 is the first stable format |
| 3 | Agent-readable | reachable by a machine | Near-standard among leading systems. 20 of 21 open-source design systems ship an MCPModel Context Protocol. The open protocol that agents use to read tools and data. server, counting official and community servers |
| 4 | Agent-governed | ranked and checked | Frontier. No vendor sells it finished |
| 5 | Self-maintaining | proposed by agentsAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent., approved by people | Mostly demo |
How to tell where you are
- Level 1. Change one variable and a whole brand changes. No component file is touched.
- Level 2. Tokens are files in a repository. A pipeline builds them into code and a version number goes up.
- Level 3. An agent can list your components and tokens without a person pasting them: an MCP server, a registryA list of the components of a system that a tool or an agent can read. or
llms.txt. - Level 4. Your rules are numbered. When two files disagree, a declared order decides. Each rule names the check that enforces it, and the check runs in CIContinuous integration: the checks that run on each change of the code..
- Level 5. Agents propose changes to the system. A person approves each one before it merges.
Levels 1 and 2 are not obsolete. In 2026 they have free, open parts that work without a language model: DTCG for the token format, Terrazzo for the build and the checks, shadcn/uiA set of open-source components that you copy into your code. Agents know it well. or Basecoat UIThe look of shadcn/ui as plain HTML and CSS, without React. for the atoms. The step from 3 to 4 is not a purchase. It is a list of decisions, an order of authority and checks.
Find your level
Six yes/no questions. The answers stay in your browser and in the address of the result. Nothing is stored or sent.