The three features
The project has a defined scope:
- Artist search,
/search/artist?q=name - Discography,
/artist/{id}/albums - Album details,
/album/{id}(tracklist, cover, date)
All endpoints come from the Deezer public API. No authentication needed, but there's a CORS issue we'll solve in the next chapter.
---Improve PLAN.md
"Review the initial PLAN.md based on AGENTS.md (or CLAUDE.md if I'm using Claude Code). Detail the implementation phases, keep each phase small and testable, add clear acceptance criteria, and suggest the simplest stack that works."
The agent will improve the draft, propose a stack, and organize execution. Don't accept automatically.
---Review and iterate
Read the entire plan and ask yourself:
- Do the phases make sense? Is each one independently testable?
- Is the scope clear? Is any phase too large?
- Is the stack simple enough? Do you understand the suggested technologies?
If something doesn't make sense, iterate:
"This phase is too big, split it in two."
"I don't want that library, suggest something simpler."
"Add acceptance criteria for each phase."
PLAN.md is detailed, saved in the repository, and reviewed by you. Each phase has acceptance criteria you can actually test.
Chapter 2
0 of 3 checkpointsComplete all checkpoints to unlock the next chapter.
Next up: Build in parts →