Push to GitHub
Your code needs to be on GitHub before Pages can work.
Prompt:
---
"Commit all project code and push to the GitHub repository. Then set up GitHub Actions for automatic deployment to GitHub Pages on push to main."
Validate the deploy
After pushing, validate each step:
- Settings → Pages in the repository: source = GitHub Actions
- Actions tab: workflow completed without errors
- Visit
https://your-username.github.io/deezer-explorer/ - Test search, discography, and album details on the published site
✓ Checkpoint:
---
Site published and accessible. All three features work on the GitHub Pages URL.
What to take from here
- Context before code, README, PLAN.md, and agent rules come before the first component
- Plan before building, an iterated plan with the agent prevents rework
- One phase at a time, SDD works because each step is verifiable
- Prompts with context, interaction quality defines output quality
- Read what the agent generates, accepting without reading is the most common failure
- Publishing is part of the flow, deployment isn't extra, it's the natural conclusion
This workflow, with context, planning, phased execution, validation and publishing, is the same one that works in real projects. The scale changes, the process doesn't.
Chapter 4
0 of 3 checkpointsComplete all checkpoints to unlock the next chapter.
Back to overview →