Taste, Adjust, Repeat

Here's a secret about the people who seem "good at AI": their first prompt isn't better than yours by much. They're just faster and calmer on the second one. The skill isn't the perfect order — it's the loop: look at the plate, say what's off, ask again.

Today we train that loop on purpose, five rounds, on the page you built in Lesson 2. Round four is a deliberate disaster. That's not a typo — breaking things on purpose, then fixing them, is the fastest known cure for the fear that keeps people from ordering boldly.

What you'll plate today

Your page, five deliberate changes better — and a nervous system that has felt a mistake get unmade. That second thing is the real dish.

Ingredients

• Your first-kitchen folder with index.html
• About 30 minutes

Cook

Open the kitchen (folder → terminal → claude) and run these five rounds in order.

Round 1 — the precise order

On my page: make the section headings slightly bigger, and give the
page a bit more breathing room between sections. Refresh my browser.

Notice the shape: where (the page), what (headings, spacing), how much (slightly, a bit). Vague amounts are fine — "slightly" is a real instruction. Look at the result before moving on. Always look.

Round 2 — the structural order

Add a small footer: just the year and the words "cooked with an AI
agent, seasoned by hand." Match the style the page already has.

"Match the style it already has" is a power phrase — it tells the agent your page is the reference, not its imagination.

Round 3 — the vague order (on purpose)

Order this exactly, badly:

Make it better.

Look at what it does. Something generic, probably fine, probably not yours. This is the most important taste of the lesson: vague in, generic out — and it's not the agent's fault. Now re-order with your actual opinion:

Undo your idea of better. What I actually want: [the one thing you
wish the page had — e.g. "my name to feel like a logo, not a title"].

Round 4 — the disaster

Trust the process:

Delete all the styling from index.html. Leave just the bare content.

Refresh. Look at it — naked, broken-looking, 1994. Feel the little spike of "oh no." Now:

Put the styling back exactly the way it was before the last change.

Refresh. It's back. That round-trip is the lesson. The fear of ruining things assumes ruin is permanent — in this kitchen it almost never is, and in Lesson 5 "almost never" becomes "never."

Round 5 — the debrief

In four plain lines: what did we change today, and which change do
you think improved the page most? Disagree with me if you like.

Reading the agent's explanation closes the loop — you'll catch it misunderstanding you before it matters, and sometimes it makes a point you'll steal.

When it burns

• "Done!" but the page looks identical — refresh harder (Ctrl+F5 / Cmd+Shift+R). Still identical? Say: "I see no difference on my screen after refreshing — what exactly did you change, and in which file?"
• The change landed in the wrong place — name the spot like you'd tell a person: "not the header — the 'learning now' section."
• It keeps apologizing and re-trying in circles — stop steering the wreck. Describe the end state fresh: "Forget the last few attempts. Here's what the section should look like: …"
• You hate everything now — "Put the page back to how it was at the start of this conversation" usually works. If it can't — that pain is Lesson 5's opening argument.

Order up

□ Five rounds ordered, five results looked at
□ You re-ordered the vague round with a real opinion
□ You broke the page on purpose — and unbroke it
□ You can say the loop out loud: look, say what's off, ask again

Next up — Lesson 04: The Kitchen Notebook. You've now repeated yourself a few times ("one file only!", "warm colors!"). Time to write the rules down once — so the agent remembers them every single session.

Stuck on a step? Question box below — that's what it's for.