Bring spec, prompting, review, tests, and a ship checklist together to finish a mini app like Quick Notes.
Let's think about it this way for a sec
This lesson pulls everything from the previous lessons into one flow. Write the spec. Build the first file. Align the UI with tokens. Store the data. Review it. Add tests. Check for secrets. Only then think about the next feature. Success in vibe coding isn't measured by how much AI wrote — it's whether what's left is something you understand and can actually use.
Connecting it to everyday life
Suggested project: Quick Notes. List, add, delete, localStorage, empty state. No login needed. Use the prompt patterns from lessons 5–8. Commit each piece as you go. At the end, write a list of 'files I understand.' If any file is left that you don't understand, either have it explained or delete it.
Let's try it together
Quick Notes definition of done
[ ] I can add a note
[ ] I can delete a note
[ ] Refresh keeps my notes
[ ] Empty state is visible
[ ] Keyboard can reach Add and Delete
[ ] No API keys in the repo
[ ] I can explain every file I keptYou'll finish a vibe-coded mini app that you understand and that actually works.5-Minute Try-It
Finish Quick Notes, or your own spec. Check off every box, and write notes on two AI mistakes you ran into and how you fixed them.
A Quick Word of Caution
Never treat AI output as automatically correct. Have a human read through the code and test it — and double-check secrets and user data — before you rely on it.