Lesson 3 of 12 · 3 min read

How do you write design quality down so an agent can use it?

Put it in three places: a design system that says why, not only what; checks that run on every change; and a definition of done written before the build starts. Judgment used to spread through reviews and handoffs. With agents building, it has to live in the system.

Diagram: a questionable pair of primary buttons in the design system becomes a written rule, then an automated check; the definition of done still keeps a designer review.
A questionable pair of buttons became a rule, then a check. A designer still reviews the rest.

If designers own “ready to ship,” quality can’t stay a feeling

At uxcon vienna, a UX conference, Meaghan Choi described design collapsed into two loops: decide what to build, and decide when to ship. Dmitry Sergushkin’s answer, on LinkedIn: the second loop needs a definition, and the definition needs a home.

Three places design quality can live where an agent will find it
  1. The systemread before buildingAn undocumented decision becomes an agent’s error
  2. The checksrun on every changeColors, sizes, contrast, and content rules, measured, not reviewed
  3. Donewritten firstPeople and agents ship against the same bar

His evidence: every mistake his team’s AI coding agent made traced back to a gap in their design docs, and each gap became a rule.

Every rule on this site came from a failure I found first

This site, my portfolio, is held to four written specs by twelve checks that measure the rendered page.

The homepage of this site at laptop width: the wordmark and navigation, a portrait in a circle, and the title beside it.
From my work This site. Every color, size, and space on the page is held by a written spec and a check. Read how I built this site
Three failures, and the check each one became
  1. A captionshipped too faint over a photo; now a check reads its contrast pixel by pixel
  2. A prototypepassed while the checks saw a sixth of it; now they press every button
  3. The specsdrifted from the site’s code three times; now every color and size they name is checked

A rule I’d once have written down and hoped to remember is now a script that refuses any change that breaks it.

A passing check only proves what it measures

Some quality can’t be a script. In a simulated run of Agent Review, my prototype of product design with AI agents, every check passed a cancel link styled to be easy to miss. No check could say whether that was on purpose.

I knew its history, so I wrote the answer where the next agent would read it: on the billing screens, an action that ends a subscription is never styled to be easy to miss.

This has a cost: the site is slower to change than a template. I think that’s the right price.

Judgment used to scale through people. Now it has to scale through what the system can read.

Check yourself

What did your last design review catch that no document would have?

That’s a rule waiting to be written. If it comes up twice, it belongs in the system or in a check.

Is your definition of done written before the build, or argued about after?

An agent can only meet a bar it can read. A bar set after the fact is a review, not a definition.

The idea: Dmitry Sergushkin, on Meaghan Choi’s uxcon vienna talk. The example: How I built this site.