Judgement and taste
Taste as a record
A dated record of how you react to designs and wording. AI coding agents, the models that write and run code in a project, may add to it, and only you can promote an entry to a rule. It is the decision record, a short dated note of one decision and whether it was proposed or accepted, applied to taste.
One of 15 patterns I've found working with AI coding agents. An agent drafted the words from my notes, and I haven't edited them yet. See all 15, or read how they are made.
An agent drafted the words from my notes, and I haven't edited them yet. The code was run before it went in.
The problem
Agents make dozens of small visual choices you did not ask for: a shadow under a button, a spinner, an exclamation mark. Most are what the model reaches for by default. You reject one, and the agent's next session, a fresh run that starts without the earlier conversation, puts it back, because nothing it reads remembers that you said no.
One prototype of mine went through five rounds of rejection in two days, each aimed at a generated default. Every rejection sat in a chat that the next session never saw.
The obvious fix is to let the agent write a rule each time you object. That has its own catch. In my experience an agent tends to turn one remark about one screen into a rule for everything, and the rules soon become its guesses about you, not your decisions.
The idea
Split the record in two. Observations are dated reactions in your exact words, with what was on screen. Any agent may add one, and an observation is not a rule. Rules are what you have declared: each reads "never X; instead, Y", cites the observations behind it, and records who declared it, when, and in what words. The files below call you the owner.
A decision record marks each decision as proposed or accepted. Here the difference is who may change that mark: an agent can propose a rule and point at the evidence, and only you can accept it.
Two more parts. Each rule names where it is enforced, such as a lint rule (a check a script runs over the code) or a test, or says "not yet enforced". And tensions, two things you want that pull against each other, are logged with a date and left open. An agent working on a design does not get to settle one by picking a side.
Before any design work, an agent reads the rules and the open tensions, then asks of each visible element: chosen or defaulted? If nothing chose it, the agent replaces it or asks.
A version small enough to read
My own record is three plain text files in a folder of its own, with no code in it. The rules file comes first. The entries below are made-up examples in its format.
# TASTE.md
What looks chosen and what looks defaulted, for one person, across everyproject they build. Agents read this before any design work. Only the owneradds to it; agents propose in `observations.md`.
## Principles
- Taste reads as removal. Most of what a generator adds to look designed is what the owner takes away.- One deliberate signature per screen, not one per element.
## Hard rejections
Each is "never X; instead Y", with the date it was declared and where it isenforced. "Not yet enforced" means agents are told, and nothing checks.
- **Never a coloured band along the top of a card; instead, no band.** Declared 2026-10-17. Not yet enforced.- **Never a title in a colour; instead, titles in the normal text colour, and colour on a chip or an icon.** Declared 2026-10-24. Not yet enforced.- **Never a filled button for a suggestion; instead, an outline.** A filled control means the person's own answer. Declared 2026-10-24. Not yet enforced.- **Never a label that starts lower case; instead, sentence case.** Declared 2026-10-24. Enforced by a test over the copy file.- **Never pure black on pure white; instead, a tinted pair.** Declared 2026-07-26. Enforced by the colour tokens.
## Thresholds
- Body text no smaller than 16 pixels; whole-pixel sizes only.Agents write to the observations file, the same day, in my exact words. The arrow marks the ones I promoted.
# Observations (the agents' inbox)
Agents append here, the same day, dated, in the owner's exact words. None ofthis is a rule. The owner promotes an entry into TASTE.md or strikes it.
- **2026-10-17**: A card on a stats page with a coloured band along its top: "that band is what every generated card has". → Promoted the same day.- **2026-10-20**: A list of notes in a box with lines between the rows: "why is everything in a box?", and of a settings screen in boxes, "that one's fine". Proposal: content lists open, boxes for settings. Not promoted.- **2026-10-24**: A suggested answer drawn as a filled button: "it looks like I've already said yes". → Promoted the same day.- **2026-11-02**: A loading spinner on an empty screen: "what is it waiting for?" Seen once. Not promoted.The third file is the list of open tensions.
# Open register
Two things the owner wants that pull against each other. Dated, and neverresolved by an agent: an entry is closed only by a dated line from theowner striking it.
- **2026-07-26: Warm against merely not stark.** The owner has always asked for warm paper, and also said stark black and white is the real problem. The stable part is the contrast ceiling; the warmth may be habit.- **2026-10-24: Colour with one job, against more colour.** One project keeps colour for one meaning; another asks for more colour. Per project until the owner rules.What makes the files work is an instruction every design session loads first: read the rules and the open tensions, then go through every visible element and ask whether it was chosen or defaulted. This is that instruction, cut down to a review of one screen.
You are about to change a screen for an owner whose taste is recorded below,in TASTE.md and the open register. Before you change anything, go throughevery visible element of the screen and ask: was it chosen, or defaulted?
For each element, say which it is. Where an element breaks a hard rejection,quote the rejection and give its replacement. Where a question is one of theopen register's tensions, say so and leave it for the owner; do not resolveit. Do not add rules of your own, and do not treat anything outsideTASTE.md as a rule.A short script gives the instruction, the rules and the open tensions to a model through the command line of Claude Code, Anthropic's coding agent, with one screen to review, a product card that an AI design tool generated. The observations stay out: they are not rules.
<div class="card" style="border-top: 4px solid #6d4aff; box-shadow: 0 4px 12px rgba(0,0,0,.15); border-radius: 12px; padding: 24px; background: #ffffff; color: #000000"> <h3 style="color: #6d4aff">weekly summary</h3> <p style="font-size: 14px">You closed 12 notes this week, 3 more than last week.</p> <button style="background: #6d4aff; color: #fff">Archive the old ones (suggested)</button> <button>Keep them</button></div>// Load the record, then test every element of a generated screen against it: chosen or defaulted?// Run: bun review.ts card.html. Needs the claude CLI, logged in. Costs a few cents.import { mkdtempSync, readFileSync, rmSync } from "node:fs";import { tmpdir } from "node:os";import { join } from "node:path";
const read = (f: string) => readFileSync(join(import.meta.dir, f), "utf8");// What the agent is given: the instruction, then the record. Observations are not rules, so they stay out.const system = [read("review.md"), read("TASTE.md"), read("open-register.md")].join("\n\n");const ELEMENTS = { type: "object", properties: { elements: { type: "array", items: { type: "object", properties: { element: { type: "string" }, verdict: { enum: ["chosen", "defaulted", "breaks a rejection", "open tension"] }, rule: { type: "string" }, instead: { type: "string" } }, required: ["element", "verdict"] } } }, required: ["elements"] };
const cwd = mkdtempSync(join(tmpdir(), "taste-"));const r = Bun.spawnSync(["claude", "-p", "--model", process.env.TASTE_MODEL ?? "claude-sonnet-5-5", "--safe-mode", "--setting-sources", "", "--tools", "", "--no-session-persistence", "--system-prompt", system, "--json-schema", JSON.stringify(ELEMENTS), "--output-format", "json"], { cwd, stdin: new TextEncoder().encode(`The screen:\n\n${readFileSync(process.argv[2] ?? "card.html", "utf8")}`) });rmSync(cwd, { recursive: true, force: true });const { elements } = JSON.parse(r.stdout.toString()).structured_output as { elements: { element: string; verdict: string; rule?: string; instead?: string }[] };for (const e of elements) console.log(`${e.verdict}: ${e.element}${e.rule ? `\n rule: ${e.rule}` : ""}${e.instead ? `\n instead: ${e.instead}` : ""}`);Run with Bun, a JavaScript runtime, one real run returned:
breaks a rejection: Coloured 4px band along the top of the card (border-top: 4px solid #6d4aff) rule: "Never a coloured band along the top of a card; instead, no band." (declared 2026-10-17, not yet enforced) instead: Remove the band. Don't swap in another border.breaks a rejection: Title colour (#6d4aff on the h3) rule: "Never a title in a colour; instead, titles in the normal text colour, and colour on a chip or an icon." (declared 2026-10-24, not yet enforced) instead: Set the title in the normal text colour. If the purple is kept, put it on a chip or an icon.breaks a rejection: Title text "weekly summary" rule: "Never a label that starts lower case; instead, sentence case." (declared 2026-10-24, enforced by a test over the copy file) instead: "Weekly summary". Change it in the copy file, since that is where the test looks.breaks a rejection: Text and background pair (#000000 on #ffffff) rule: "Never pure black on pure white; instead, a tinted pair." (declared 2026-07-26, enforced by the colour tokens) instead: Use the tinted pair from the colour tokens instead of hard-coded hex values.open tension: How warm the tinted pair should be rule: Open register, 2026-07-26: "Warm against merely not stark." The contrast ceiling is stable, but the warmth may be habit. instead: Left for the owner. The rejection only requires the pair not be pure black on pure white. I won't decide whether it should be warm paper.open tension: Purple (#6d4aff) as the screen's colour, on the band, the title and the primary button rule: Open register, 2026-10-24: "Colour with one job, against more colour." It is decided per project until the owner rules. instead: Left for the owner. The rejections above still apply to the band, the title and the button. Whether purple keeps one meaning or the screen gets more colour is not mine to settle.breaks a rejection: Body line "You closed 12 notes this week, 3 more than last week." at 14px rule: Threshold: "Body text no smaller than 16 pixels; whole-pixel sizes only." This is a threshold, not a never/instead rejection. instead: 16px or larger, in whole pixels. The wording is not in question.breaks a rejection: Filled purple button "Archive the old ones (suggested)" rule: "Never a filled button for a suggestion; instead, an outline." A filled control means the person's own answer. (declared 2026-10-24, not yet enforced) instead: An outline button, with no fill. The button's own label already says it is a suggestion, so the fill only repeats that.defaulted: "Keep them" button (unstyled browser default) rule: No rejection applies. It has no styling at all, so nothing shows it was chosen. instead: Nothing is required by TASTE.md. It needs a deliberate treatment, and the fill rule above bears on which button, if any, is filled.defaulted: Drop shadow (0 4px 12px rgba(0,0,0,.15)) rule: No hard rejection covers it. The only relevant guidance is the principle "Taste reads as removal." That is a principle, not a rule I can enforce. instead: Nothing is mandated. It looks like generator decoration, so I'd flag it to the owner rather than remove it myself.defaulted: Card shape and spacing (12px radius, 24px padding) rule: Nothing in TASTE.md speaks to radius or padding. instead: Nothing is mandated. I'll leave these as they are, and they're the owner's call.It found all five things the card breaks, and quoted the rule for each. It left both tensions open, as told. It noticed that the two rules that have a check behind them would not catch this card, because its words and colours are typed straight into it. And it did not invent a rule for the shadow: no rule covers it, so it flags it for the owner.
Most of the rules say "not yet enforced". That is true of mine too. The record is loaded by an instruction, not by a check, so a session that skips the instruction skips the record.
Where a plain style guide falls short
The plain form is a style guide, a page of do and don't pairs that agents are told to read. I've met each of these gaps.
- Rules you did not declare. An agent that may write the rules will write its own reading of you into them. Keeping promotion for you keeps the rules yours.
- A ban with no replacement. "Never a drop shadow" sends the agent to its next default. "Instead, a one-pixel outline" tells it what to use.
- A paraphrase drifts. "Looks generated", written down as "prefers flat design", is a different rule. The exact words, quoted, show what was actually said.
- One screen's reaction becomes taste. Keep three places apart: your own taste across projects, rules a project has decided, and raw reactions on a project. A remark about one screen starts in the last of those.
- A rule passes for a check. Writing where each rule is enforced, or "not yet enforced", stops a sentence in a file from looking like a test.
- A tension is settled quietly. When two things pull against each other, an agent will often pick one in the work and move on. Logging the tension open, and refusing an agent's attempt to mark it settled, leaves the choice with you.
Trade-offs
- Most of it is an instruction, not a check. In my own setup, agents are told to read the record before design work, and nothing fails if one doesn't. Only a rule with a test or a lint rule behind it can stop a change going in.
- Promotion waits on you. My own record has 79 dated observations since July, and the observations on one topic have been promoted to rules so far. The rest are proposals. That is the design working, and it is also a queue that only one person can clear.
- A name in a field is not a signature. The record says who declared each rule, and an agent can write your name there. Promotion is held by an instruction, not by anything that checks who wrote the line. A stronger version would accept a declaration only from a change you made yourself, such as a commit (a saved change in git, the tool that keeps a project's history) that you authored.
- Avoiding defaults is not the same as having taste. A list of things never to do removes the commonest defaults and leaves you somewhere generic. A warm off-white with an earthy accent that I once chose for a site of my own later became a look AI tools produce by default. Only specifics make the work yours: named references (particular sites, books or designers you point to), declared tensions, one deliberate signature element.
When to use it, and when not to
It suits anyone who reviews screens or wording that agents made, often enough to find themselves saying the same thing twice. It is more than a one-off page needs, and it is the wrong place for decisions a team makes together, which belong in the team's own decision records.
Example. The taste record and its check, on GitHub
A draft skill for this pattern
A skill is a short set of instructions you give a coding agent so it applies a pattern the way you would. Copy the text below into a file called SKILL.md, in the folder your coding agent reads skills from. In Claude Code, Anthropic's coding agent, that is .claude/skills/taste-record/. It is a draft, and I haven't tried it on anyone else's project yet.
---name: taste-recorddescription: Use before any design or interface work, when the owner reacts to how something looks or reads ("that looks generated", "take that off"), and when tempted to turn a reaction into a rule. Keeps a dated record of reactions that agents may add to and only the owner may promote.---
# Taste record
Agents tend to ship the defaults their models reach for. A person rejectsone, the next session makes it again, because nothing it loads remembers therejection. A taste record is the memory: reactions written down as theyhappen, and rules the owner has declared from them.
## Before design work
1. Read the record's rules and open tensions before you draw or write anything the owner will see.2. For every visible element, ask "chosen or defaulted?". If nothing in the record or the brief chose it, say so, and replace it or ask.3. When you hand design work to a sub-agent, paste the hard rejections into its brief and tell it to read the record. A sub-agent has not loaded what you loaded, and will reach for the same defaults.
## When the owner reacts
1. Append one dated observation: the date, what was on screen, and the owner's exact words in quotation marks. Do not paraphrase, and do not generalise to a rule.2. Write it where it belongs. Keep three places apart: the owner's own taste across projects, rules a project has decided, and raw reactions in a project. A reaction to one screen is not yet personal taste.
## Rules
1. Never promote an observation to a rule yourself, however often it recurs. You may propose one, citing the observations behind it.2. A rule is locked only when the owner declares it. Record the declaration: who, when, and their words.3. Write each rule as "never X; instead, Y". A ban with no replacement sends the next agent to its next default.4. Say where each rule is enforced (a lint rule, a test, a checklist), or write "not yet enforced". Most rules start there; say so rather than imply a check exists.
## Tensions
When two things the owner wants pull against each other, log the tensionwith its date and leave it open. Do not resolve it, and do not pick a sidequietly in the work. Only the owner closes one.
## What it does not do
It does not make the work look like anyone in particular. A list of thingsto avoid only removes the commonest defaults, and a look the owner oncechose can become a default itself. Only specifics (named referencessuch as particular sites, books or designers, declared tensions, onedeliberate signature) make it theirs. Nor doeswriting a rule down mean anything reads it: if the record is loaded by aninstruction rather than a check, an agent can still skip it.