Graduation Dinner

Nine lessons ago, a terminal was intimidating. Since then you've built pages by talking, taught a project your taste, made mistakes reversible, put your work on the internet, pointed the machine at your own data, scheduled work to happen without you, and given your agent eyes. Every lesson handed you the recipe.

This one doesn't. Graduation dinner is the meal you choose. The only requirements: it's yours, it ships, and one real person sees it.

What you'll plate today

A project that didn't exist this morning — planned by interview, built in the loop, saved at every step, live at a URL, served to someone who matters.

Ingredients

Everything you've learned (it's enough — that's the point)
1–2 hours, ideally one sitting
One person in mind to serve

Cook

1. Choose your dish (ten minutes, not two days)

Three shapes that make excellent first solo projects, because they're one-file, one-sitting, no-login dishes:

A gift — a tiny tool for one specific person: a countdown to your friend's marathon, a converter for your dad's hobby units, a "which restaurant tonight" spinner for your partner.
A post — a page for a thing you organize or love: the family trip plan, your club's schedule, your top-ten anything with strong opinions.
A toy — a small game or amusement: a reaction timer, a daily coin-flip ritual, a fortune cookie with your fortunes in it.

The trap to dodge: ambition. "A booking system for my gym" is a wonderful fifth project. Graduation dinner is judged on shipped, not on scope — pick something that fits in one sitting, and pick for a specific person. Dishes for someone always beat dishes for everyone.

2. Plan by interview (Lesson 2's move, promoted)

New folder, new kitchen — order this:

Today I'm cooking my own dish, start to finish.

Interview me: ask up to five questions, one at a time, to pin down
(1) what exactly we're building, (2) who it's for, (3) what "done
tonight" looks like — the smallest version that would still delight
that person.

Then set up this new project: CLAUDE.md with the house rules I
dictate, save points from the start. Then propose a plan of three
steps and wait for my go.

Dictate your house rules from memory — you know them now. Notice what you're doing: you're not following a course anymore. You're running a project.

3. Build in the loop

Work the plan step by step. You know the physics:

Look, say what's off, ask again (Lesson 3)
Save point after everything you like (Lesson 5)
Vague in, generic out — order with opinions (Lesson 3)
Stuck or spiraling? Describe the end state fresh, or restore the last save and take a smaller bite

If the scope starts swelling mid-build — it will try — use the professional's sentence: "Cut it down: what's the smallest version that still delights?"

4. Ship and serve

Pre-flight check this page like a stranger (anything private?),
then deploy it with Cloudflare Pages under [NAME]. When it's live,
open it with your browser, check it at phone size, fix what's off,
ship again, and confirm. Save point: "graduation dinner served".

One prompt, four lessons' worth of workflow. Then the part no terminal can do: send the URL to the person it's for. Not "look what AI made" — send it as what it is: "made this for you."

5. The last order of the course

Write a short note in CLAUDE.md titled "what the chef learned":
three things I now know how to do that I didn't ten lessons ago,
in my own words — ask me for them, don't invent them.

Answer honestly. That note is for the you who opens this folder in six months.

When it burns

Frozen at step 1 — choose the person, not the project. Who'd smile at a link from you tonight? Build toward that smile.
Halfway in, it's a mess — restore the last good save point (this is why they exist), then take smaller steps.
The agent lost the plot on a long build — long sessions drift. Start fresh: "Read CLAUDE.md, look at the project, summarize where we are — then we continue."
It's done but you're embarrassed to send it — that feeling is the last boss of the course, and it lies. Simple and shipped beats impressive and imaginary. Send it.

Order up — the final pass

□ A project you chose, planned by interview, built in the loop
□ Save points from first commit to "graduation dinner served"
□ Live at a URL — verified by your agent's own eyes
□ One real person received it, from you

All checked? Then here's what's true now, and no one can un-true it: you are someone who ships. Not "learning to code" — cooking, with an agent, from idea to internet, on your own judgment.

After graduation

Your kitchen stays open. Three ways to keep cooking:

The recipes — every single-dish technique we publish, from remote-controlling your agent from your phone to what to try when models disagree.
Subscribe — new recipes and lessons as they leave the kitchen.
Show us your graduation dinner at @AgentKitchenHQ — we mean it. This kitchen grows by cooks showing each other what they made, and your project might be exactly the push the next reader needs.

And if any lesson left a hole — the question box below is permanent. Graduates' questions are how the next class gets a better course.

Order up. 🍳