Design systems & AI

AI readiness for design systems

Why agents average your copies, and the contract they need. Thirty minutes.

Christoph Hellmuth · Design Engineering Studio

The reality

The agent averages the copies.

When the doc, the token, and the code disagree, an agent does not ask.

Punched card machines at Bletchley Park, 1945.

Machines execute the pattern you give them.

The diagnosis

Connecting MCP does not reconcile the copies.

It gives the disagreement a faster distribution across your git history.

Structure

Three copies. Then the compiler.

  1. 01
    The Three Copies

    Where documentation, tokens, and component code drift apart.

  2. 02
    Machine-Readable Contracts

    Why human markdown fails and AST schemas succeed.

  3. 03
    Code Connect & Strict ASTs

    Mapping Figma canvas nodes directly to verified React imports.

  4. 04
    The AI Readiness Audit

    A four-step checklist to run before connecting any coding model.

Part 01

The three copies

Where the drift hides before you prompt.

The triangle

Doc, token, component.

  1. 01
    The Documentation

    Written in Storybook or Notion. Describes what someone hoped was true two quarters ago.

  2. 02
    The Token

    A variable in Figma or a JSON file. Updated during a rebrand, but disconnected from runtime builds.

  3. 03
    The Component

    The actual production React code. Full of local hotfixes, unvetted props, and inline style overrides.

Precedence

Establish which copy wins in a conflict.

The semantic token contract wins, code follows, and breaking changes require a version bump.

A woman punching cards at a pantograph, circa 1940.

One punch. One record.

Hallucination

Agents do not hallucinate out of malice.

They hallucinate because your component interface was too loose to constrain them.

Part 02

Machine-readable contracts

Moving beyond human markdown.

Format contrast

Human prose vs machine schema.

01Human Markdown

'Buttons should generally have generous padding and feel primary when placed on light backgrounds.' Vague, subjective, impossible for an agent to verify in code.

02Machine Schema

Strict JSON schema with typed prop unions, bound design tokens, and WCAG contrast assertions. 100 percent deterministic for both linters and agents.

Tokens

Point the agent at the package, not raw CSS.

The prompt must inject the component import manifest, not a Tailwind cheat sheet.

Jacquard loom at Museum Tuch und Technik showing punched card sequence.

The cards dictate the weave.

Code Connect

Code Connect is the map.

  1. 01
    Figma Node ID

    The exact unique identifier of the component symbol on the canvas.

  2. 02
    The Connect Mapping

    A small code contract declaring props, variants, and subcomponent bindings.

  3. 03
    Production Import

    The verified React or web component snippet injected into code when the node appears.

Taxonomy

A token file agents can parse is small and boring.

Flat key-value hierarchies with semantic paths beat deeply nested ambiguous JSON objects.

Part 03

The AI readiness audit

Four checks to run before connecting an agent.

Checklist

The four-step AI readiness audit.

  1. 01
    Eliminate Orphan Tokens

    Grep your repository. Any token in Figma or JSON with zero production imports must be purged.

  2. 02
    Enforce Prop Parity

    Verify that every variant in your Figma library corresponds 1-to-1 with a TypeScript prop interface.

  3. 03
    Commit Code Connect Mappings

    Wire your core twelve components so agents have an unambiguous path from canvas to code.

  4. 04
    Install Linter Guardrails

    Add ESLint rules that block pull requests containing hardcoded hex, raw pixel spacing, or detached components.

Herbarium sheet with labeled botanical specimen.

Classified, pressed, and labeled.

Quality bar

The quality bar moves to the prompt and the gate.

You no longer spend hours writing boilerplate div tags. You spend minutes reviewing the diff.

Comparison

Unready team vs AI-ready studio.

01The Unready Team

Connects Cursor to messy legacy repo. Gets 50 new rogue buttons. CSS payload balloons by 45 percent. Maintenance consumes 60 percent of sprint capacity.

02The AI-Ready Studio

Strict token contract, Code Connect mapped, automated CI gates. Ships production features 4x faster with zero design drift.

Part 04

The quarter ahead

What to do on Monday.

Action plan

Start with one component, not the entire library.

Take your Button. Align the doc, the token, and the props. Wire Code Connect. Test it with an agent.

Conclusion

Agents need contracts, not pictures.

Build the machine-readable system before you press generate.

Christoph Hellmuth · Design Engineering Studio

The question

Is your system machine-readable, or only human-plausible?

Test it this week: ask an agent to build a form using only your library. Look closely at the diff.