§0problem
← All case studies

An agent-first design-system foundation

Level 4, partly 5 · 2026 · for a banking software vendor

An agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. asked to build a banking screen writes plausible HTML, invents values and drifts from the system. Reviewing that output costs more than writing it.

§1built

What was built

The agent never writes HTML. It writes a typed page specA structured description of a page that a script turns into HTML. The agent fills the spec. It does not write the HTML.. A script composes the page from vetted parts and returns a verdict. The agent selects and fills; scripts build and judge.

  • TokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format. in 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, built with Terrazzo. About 1,618 token definitions in four tiers 2 brands × 2 modes = 4 CSS permutationsOne combination of the modifier options. This site has four. from one resolverThe part of a token set that selects the values for a context, for example a brand or a mode.
  • 41 components Fidelity pass over 34 components, 368 variants, 4,445 checks, 30 accepted deviations
  • 38 numbered 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.; the build fails when 'Enforced byThe field of a decision that names the check that proves it, or says "not enforced (gap)".' is empty
  • An order of authority across the rule files.
  • SkillsA file that tells an agent how to do one task. In my method, a skill applies a rule. It does not make one. that apply rules and never make them.
  • A do-not list that names likely hallucinationsSomething that an agent invents, for example a component name that does not exist. with their replacements.
  • A proposal path, so a missing part becomes a proposal and is not invented.
  • A rule against invented content: no made-up money values or names. Invented content caused 5 of 21 defect fixes on an earlier project
Built in two weeks
§2taught

What it taught

Restructure the task so the error cannot happen. A typed spec removes whole classes of defect that review would only catch some of the time.

The design file is evidence. A reference page matched its design in 41 of 41 boxes; following the component masters, 29 of 41

§3open

What is still open

These are the credibility. I show them.

  • 11 of 25 planned rules not built
  • Skills not yet wired to the agent
  • 15 proposals approved without review