Prove It: Module 2 Check
A post-test on the loop, plus what changed since the start of the module.
📈 Compare, Don’t Just Answer
One of these revisits the prediction you made at the start of the module. See what’s different now that you’ve actually run the loop three times.
1. Your app's button doesn't do what you expected. What's the best next move?
Describe, test, refine, repeat — you ran this three times last lesson. It's the whole method.
2. Which of these refinement requests is most likely to get you what you actually pictured?
Specific, and it names both the current state and the desired one. The other three give the AI nothing concrete to act on.
3. How many rounds of adjustment does a typical vibe-coded app go through before it's genuinely good?
You proved this yourself — your app got meaningfully better across three separate rounds, not one perfect attempt.
🎉 Celebrate, Revisited
Look back at how you reacted the first time your Module 1 app didn’t quite work, versus how you reacted during Round 1 of this module. If the second time felt more like “okay, let’s fix this” and less like “I did something wrong” — that shift is the actual point of this module. The loop isn’t a fallback for when things go badly. It’s the normal, expected shape of building anything.
⏭️ Up Next
So far, refining has meant telling the AI what looked wrong. Module 3 goes one level deeper: what to do when the app doesn’t just look wrong, but actually breaks — and why that’s still nothing to be afraid of.