This chapter gives you the 3 checklists to follow at every key step: starting a project, shipping a feature, and ending a session. Print them or keep them within sight. Reading time: 5 minutes.
Checklist 1, before starting a project
Everything that needs to be in place before you write the first line of code.
Installation - [ ] VS Code installed with the Claude Code extension - [ ] Active Anthropic subscription (Pro or Max) - [ ] First launch successful and signed in
Project setup - [ ] CLAUDE.md created with the 8 sections (chapter 3) -
[ ] .claude/commands/ folder created with your specialized agents (chapter
7) - [ ] .claude/settings.local.json file with pre-authorized permissions
(chapter 9) - [ ] docs/plans/ folder created for design docs and plans - [ ]
MEMORY.md initialized (chapter 10)
Advanced configuration (optional) - [ ] Hooks configured: Prettier
auto-format, TypeScript pre-commit, end-of-session notification - [ ] Global
deny list in ~/.claude/settings.json (rm -rf, force push, db reset) - [ ]
MCP servers connected (Notion, Supabase, Vercel based on your needs) - [ ]
Exploration sub-agents created in ~/.claude/agents/ - [ ] Status line
configured with context alert
Infrastructure (if SaaS) - [ ] Node.js v22+ installed for Next.js projects
(node --version) - [ ] Supabase configured (project created, keys retrieved)
- Vercel linked to the GitHub repository - [ ] Environment variables added
to
.env.local- [ ] Domain purchased and configured (when ready for production)
Checklist 2, for every feature
The full cycle to follow for each feature, from brainstorm to commit.
Planning phase - [ ] Brainstorm, explore 3-4 options before choosing - [ ] Design doc, document the WHAT (product vision, user stories, business rules) - [ ] Implementation plan, document the HOW (numbered tasks with files and checks) - [ ] Read through and validate the plan before execution
Execution phase - [ ] "Run the plan", Claude codes, you supervise - [ ] Typecheck passes after each task → ✅ - [ ] Lint passes after each task → ✅
Validation phase - [ ] Visual test on localhost:3000, happy path - [ ] Visual test, error path (bad input, empty data) - [ ] Responsive test, shrink the window to simulate mobile - [ ] French copy with correct accents - [ ] Iterations (2-3 visual or functional tweaks)
Shipping phase - [ ] /review, hunt for bugs and weak spots - [ ] Fix the
issues flagged by the review - [ ] /commit, save with a descriptive message
- Unit tests passing (if business logic)
Checklist 3, at the end of a session
What needs to be done before leaving the dev session.
Save - [ ] All changes are committed (no unsaved work in progress) - [ ] "Update the project memory", save what you learned
Prepare for the next session - [ ] Note the next priorities (in
MEMORY.md or a dedicated file) - [ ] If a bug is still open, document it
clearly - [ ] Push the code to GitHub if needed (git push)
"Quick" version for days when you're in a rush
If you only have 30 minutes, here's the bare minimum:
Express (30 min) 1. Open the project in VS Code + Claude Code 2. Describe
your feature in a sharp prompt (chapter 4) 3. Claude codes, you supervise 4.
Quick visual test on localhost 5. /commit to save 6. "Update the memory"
Takeaway: these checklists are your safety net. They make sure you don't skip any critical step, even when you're in the flow and moving fast. Keep them within reach.