The bug-report prompt and Debug mode
Write a bug report the AI can act on first time, ask for a diagnosis before a fix, and use Cursor's Debug mode for bugs that don't show any error.
Why this matters
"It's broken, fix it" is the most common prompt beginners send when something goes wrong. Sometimes it works. Often the AI guesses, changes three files, and creates a new problem while "fixing" one it imagined.
The AI isn't being careless. It can't see your screen. It doesn't know which page you were on, what you clicked, what you expected, or what you changed ten minutes ago. Every gap, it fills with a guess. You learned this in Module 2 about building ("vague prompts get average websites"), and it's even more true for fixing.
In Lesson 0.4 you got a Simple help prompt. This lesson upgrades it into a full bug-report prompt, using everything you've learned in Modules 4 and 5: the file and line, where the error appeared, what DevTools showed, what changed since your last commit. You'll also meet Cursor's Debug mode, a tool built for the hardest kind of bug: the one with no error at all.
In the full lesson
- The idea in plain English
- Do it
- Check it worked
- Understand what AI wrote
- 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.