The build loop: change, preview, commit
Learn the loop you'll use for every website (one change, preview, check, commit), and save your work with Git commits, from Cursor's Source Control panel and from the terminal.
Why this matters
Here's a story that happens to almost every beginner who builds with AI. The page is looking great. They ask for one more change. The AI rewrites half the file. Something breaks. They ask it to fix that, and it breaks something else. Twenty minutes later, the page that looked great is a mess, and there's no way back to it.
Professionals don't avoid this by being more careful with the AI. They avoid it by saving a version every time something works. Then a bad change costs them one click, not their evening.
The tool for this is Git, which you installed in Module 1. Your Level 4 app is already a Git project: create-next-app set that up for you in Lesson 2.3. In this lesson you'll save your first versions in it, and learn the four-step loop you'll follow for every change from now on. Module 3 uses this loop from its first build, and in Module 3 Git is also how your website gets onto the internet.
In the full lesson
- The idea in plain English
- Do it
- The prompt
- Check it worked
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.