Today the site grows a real feature — and you learn the pattern that makes any instruction to Claude Code land right the first time.
Video script (for recording): "Welcome back. Yesterday was the smallest possible ask. Today's bigger, so we're adding structure to how you ask — four parts, and you'll never write a vague prompt again."
Install Claude Code, ship your first live page
Turn a plain-English idea into a working page
Edit what it built — ask for changes without breaking things
Understand what got created: files, folders, why they matter
Connect to GitHub so your work is never lost
Get a site live: your first real deploy
Fix things when they break — read errors without panicking
Add a second page and link it up: your landing page
Automate updates: push once, redeploy every time
Ship the deliverable: portfolio + business landing page, live
Yesterday you asked for a page in one loose sentence and it worked because the ask was tiny. Today's ask is bigger, so vague instructions start to show their limits. Compare these two:
"Make my site better."
"Add a Services section below the bio, for a freelance web designer (persona), on the site we built yesterday (context), listing 3 services with one-line descriptions (task), styled to match the existing page (format)."
Persona, Context, Task, Format — that's the whole pattern. You don't need all four labeled every time, but if a result comes back wrong, it's almost always because one of the four was missing.
Run claude in the same project folder from Day 1.
Check that it added a new section rather than replacing something you wanted kept.
If the spacing or wording feels off, say exactly what's wrong — "the gap above this section is too small" beats "make it look better."