Drag-and-drop publishing was training wheels. Today your capstone gets the grown-up setup: save points you can restore in seconds, publishing that happens by itself on every change — and the two rules about secrets that keep your projects out of trouble.
Give your capstone save points (git), a home on GitHub, and automatic publishing through Netlify — so from tonight, every improvement goes live the moment you approve it.
You need: your my-tool folder with v0 from yesterday · the internet article read · 90 minutes.
You know save points from games: reach a safe spot, save, take the risky jump. Git is exactly that for project folders — and your agent operates it for you. The vocabulary you need is three words: checkpoint (save), history (the list of saves), restore (load one).
First checkpoint
Set up save points for this project (initialize git) and create the first checkpoint named "v0 — first working version". From now on, after any change I approve, create a checkpoint with a short description automatically. Show me the history.Step done when: the history shows checkpoint one, and the standing instruction is saved to AGENTS.md (ask it to add the rule there — you know why).
The destruction drill
Trust in save points is built exactly one way. Do the drill:
Ruin my project on purpose: delete half of the main file and make the page broken. (Yes, really.)
[open the page — admire the wreckage]
Restore the project to the last checkpoint. Show me it's identical to before the damage.✦ You just watched total destruction cost you eleven seconds. This is why professionals experiment bravely: undo is a system, not a hope.
Step done when: the page works again and you felt the click of “nothing is irreversible now”.
Put the project on GitHub
Create a free account at github.com (it's the world's storage for project histories — your future portfolio too). Then let Codex connect the wires:
Publish this project's checkpoints to my GitHub account as a new private repository named my-tool. Walk me through the sign-in when needed, and from now on, push every new checkpoint there automatically. Confirm when I can see it on github.com.Step done when: you refresh github.com and see your files and history there.
Connect Netlify to GitHub
my-tool.Step done when: Netlify shows a new site created from your repository, with its own URL.
Test the pipe — your last manual publish is behind you
Step done when: an approved change appears on the live URL without you touching Netlify.
Your capstone works. “Works” and “good” are different floors of the same building, and professionals climb between them with improvement passes — focused prompts that hunt one kind of weakness at a time. Run your first two on your capstone now:
Pass one: the hostile-user hunt
Test my tool like a hostile first-time user: empty inputs, huge numbers, wrong formats, double-clicks, phone width. List everything that breaks or confuses — most serious first, with WHERE it happens and HOW to reproduce it. Don't fix anything yet.Read the list. Then fix findings one at a time: “Fix #1, tell me what you changed, wait for me.” Verify each in the browser before allowing the next. One-at-a-time is the whole discipline — batch fixes hide new breakage.
Step done when: the top two findings are fixed and verified on the live URL.
Pass two: pick the one your tool needs most
ERROR HANDLING: find every place this tool can fail — missing file, empty input, wrong format, no internet. Make each failure caught and explained to the user in one plain sentence. Return the list of failure points and what each now says.
RESPONSIVE: audit every screen at 380px width — overflow, unreadable text, buttons too small for thumbs. Fix what you find and list each fix.
UX POLISH: walk through the main task as an impatient first-time user; narrate where you hesitate or guess. Propose one fix per confusion, smallest first; apply the ones I approve.These come from our lab's Improvement Library — browse all of them, and Day 11 hands you more.
Step done when: one full pass ran and its fixes are live.
Your tool becomes real: second feature in, live on the internet, publishing itself.
homework complete — mark the day done below
Tick when the homework above is finished — it syncs to your account.
Old you: argue with the agent about what went wrong. New you: restore the last good checkpoint (seconds), then re-apply changes one at a time, verifying each. Save points turn debugging from archaeology into replay.
Checkpoint → pushed to GitHub → Netlify notices the new checkpoint → rebuilds and republishes. Three machines cooperating, zero of them being you. That's why it's called a pipeline — and yours now runs on every approval.
Treat it as leaked no matter how fast you delete it: revoke the token (BotFather → /revoke), issue a new one, update the gateway, and add “never write secrets into files” to AGENTS.md so the agent enforces it. Deleting the file is not enough — history remembers.