Start here · Lesson 1.3
A Free AI Taste Training Template to Copy and Fill In
Blank pages slow AI taste training down. You sit down to write feedback and do not know where to begin. This post gives you a plain template for one weekly review, with a filled example next to it, so you can copy, fill and move on. The method comes from Lesson 1.3: Teach AI your taste.
Fill in four blocks, what to stop, what to keep, layout and wording, then ask the AI to save each line as a rule.
How the template works
Run it once a week on a batch of seven pieces. It has four blocks and one closing sentence. Every line you write should pass the stranger test: someone new could follow it.
The structure follows ideas in the official docs. Claude Code starts each session with a fresh context window, and CLAUDE.md files or auto memory carry knowledge forward. So the closing sentence is what makes the notes last.
The blank template
Copy this into a note or document.
Batch: [what you reviewed, dates] Stop doing: 1. [specific problem] 2. [specific problem] 3. [specific problem] Keep doing: 1. [what worked and why] 2. [what worked and why] Layout: 1. [where things go, where they never go] Wording: 1. [words and phrases to use, words never to use] Close: Here is my feedback on all seven days. Apply it to every piece, not just the ones I mentioned. Then save each point as a rule so you never make that mistake again.
A filled example
Say you run a small candle shop and review a week of product posts. This example is invented.
Batch: Product posts, Monday to Sunday. Stop doing: 1. No white outlines on text. They look cheap. 2. Never leave a single word alone on its own line. 3. No text in pale grey on light photos. Keep doing: 1. The candle is always the hero of the image, large and centred. 2. Captions open with one plain sentence about scent. Layout: 1. Text only on the left or at the bottom. Never over the flame. Wording: 1. Say "hand poured". Never say "luxury". Close: (same as above)
Fill it in step by step
- CollectPut the week's pieces in order, day one to day seven.
- ScanSkim all of them before you write anything.
- Fill StopWrite one line per repeated problem.
- Fill KeepName the pieces you would post as is, and why.
- Fill Layout and WordingBe literal about positions, colours and words.
- ClosePaste the closing sentence and send it.
Check what was saved
After you send it, open the stored rules. The Claude Code docs describe the /memory command for viewing and editing what loads. Read each line.
- Is every rule specific?
- Does any rule hold two ideas? Split it.
- Do two rules clash? Fix one.
The docs say specific, concise instructions are followed more consistently, so trim as you go.
Make the template yours
Change the headings to fit your work. A video maker might add "Pacing" and "Captions". A shop owner might add "Product shots". Keep the four ideas: stop, keep, layout and wording, close.
When to retire a line
A rule you no longer need is clutter. Each month, read the whole file and delete anything that no longer matches how you work. Short files are easier for you to read and, according to the docs, easier for the tool to follow.
No work to review yet
Fill the template using a brand you love. Collect a few of its pieces and write what you would copy. This is the starting point suggested in the lesson.
A second filled example: a short video maker
To show the template works outside images, here is another invented example.
Batch: Seven short videos, Monday to Sunday. Stop doing: 1. No music that drowns out my voice. 2. Never start with "Hey guys". 3. No more than one idea per video. Keep doing: 1. The first line states the problem the viewer has. 2. Captions are on screen the whole time, in a colour that stands out. Layout: 1. Captions at the bottom, never over the face. Wording: 1. Plain words. No jargon unless I explain it in the same sentence.
Notice how each line is something you can verify by watching.
Tips for writing good lines
- Start verbs with an action: use, put, never, open.
- One idea per line.
- Add a short reason when it helps, like "they look cheap".
- Avoid soft words such as nice, better and more professional.
What to do if a block is empty
Some weeks you will have nothing for Layout or Wording. Leave it blank. Do not invent notes to fill the template. A short, accurate list is more useful than a long, padded one, and the docs say shorter, specific instructions are followed more consistently.
Questions people ask
Can I use this template for emails?
Yes. Replace the layout block with structure, such as subject line length and where the button goes.
Where do I store the filled template?
Keep the notes anywhere handy, and let the AI save the rules in its memory file.
How often should I fill it in?
Weekly is a good start. Stop if a week passes with nothing new to add.
Will the rules always be followed?
Not always. The docs call these files context, not enforced settings, so spot check.
Where to go next
For the full week review with the template in action, open Teach AI your taste, Lesson 1.3. If you want a routine around it, read The TEACH framework for AI taste training. For setup, see Lesson 1.1.