---
title: "The ladder"
url: /ladder
description: "A five-level maturity ladder for design systems in the agent era, with a five-question self-assessment that runs in your browser and stores nothing."
---

## §0 · ladder

# 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 decision 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. DTCG 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 MCP server, counting official and community servers [claim ind-mcp-share: Field study of 21 open-source design systems and 6 platforms, data gathered 26-28 July 2026, by Kaelig Deloumeau-Prigent; source: https://state-of-ai-in-design-systems.netlify.app/; confirmed] |
| 4 | Agent-governed | ranked and checked | Frontier. No vendor sells it finished |
| 5 | Self-maintaining | proposed by agents, approved by people | Mostly demo |

## §1 · how to tell

### 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 registry 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 CI.
- **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/ui or Basecoat UI 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.

## §2 · self-assessment

### 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.

- (level 1) Do components read colour, type and spacing from variables, and never from values typed into the component?
- (level 2) Are your tokens stored as data (for example DTCG JSON), versioned, and built into code by a pipeline?
- (level 3) Can an agent fetch your components, tokens and docs by machine: an MCP server, a registry or llms.txt?
- (level 4) Are your rules numbered, with a declared order of authority when two rule files disagree?
- (level 4) Does each rule name the check that enforces it, and does that check run in CI?
- (level 5) Do agents propose changes to the system that a person reviews before each one merges?

## §3 · result

