Patterns

What I've learned building software with AI coding agents, written up as patterns you can use.

It's a kind of personal digital archaeology. I go back through the transcripts of my own sessions with coding agents, the saved record of everything they and I did, and look for the things I keep doing. The ones that hold up get written up here, then built into how I work, and I go round again. Some of them might be useful to you.

An AI agent drafts each page from my notes, and each page says whether I've edited it yet. Every one has an example you can run and a skill, a short set of instructions you can give your own coding agent.

Checks you can trust

Automated checks that hold a line in a codebase, and how to tell whether they are really looking.

Running agents

Running many coding agents at once: what each one needs from you, and what their logs can teach you.

Lists and pages that stay true

Keeping documents and lists in step with the code, so they fail a check when they stop being true.

Judgement and taste

Where a machine can score the work but a person has to decide.

  • The machine scores, only a human rejects

    A model scores a list too long to read but never removes a thing, and its verdict counts only as far as its evidence survives.

  • Taste as a record

    Agents write down how you react to a design, in your words. Only you can turn a reaction into a rule.

  • The cold reader

    A reviewer that sees only the rendered page lists every name and "the X" a first-time visitor couldn't work out.

  • Your writing voice, captured and checked

    Keep what an agent drafts in your name sounding like you: a measured profile, a check run until it passes, a cold read.