The Iterator
After this drill, you have refined your app through 5 rounds of targeted feedback and understand that iteration — not the first build — is where quality is made.
Why this matters
The single most important principle in AI-assisted building: the first output is never the final output. Quality is made in iteration. Each round of feedback should be specific, single-focused, and build on what works rather than tearing down what does not. This drill builds the iteration discipline that separates builders who ship polished products from those who are perpetually stuck on the first draft.
How to do it
- 1
List the top 3 problems with your current build
Prioritize by impact on the core user action. Not visual polish — functional gaps.
- 2
Run 5 targeted iterations using the iteration prompt pattern
Each iteration: one specific problem, one clear request, preview after every change. Do not bundle multiple changes into one prompt.
- 3
Add one visual improvement in iteration 4 or 5
Once functional issues are resolved, one pass on visual quality is appropriate. Color, spacing, typography — one thing at a time.
- 4
Describe what you would fix next if you had one more iteration
This builds the habit of conscious scope control: knowing when to stop is a skill.
The prompt
In the current version of my app: [DESCRIBE WHAT CURRENTLY HAPPENS] The problem: [ONE SPECIFIC PROBLEM — not multiple issues] What I want instead: [PRECISE DESCRIPTION OF THE DESIRED BEHAVIOR] Please fix only this one issue. Do not change anything else.
Success criteria
- ✓You completed 5 targeted iterations
- ✓Each iteration addressed one specific issue
- ✓The app is demonstrably better after the 5 rounds
- ✓You can describe what you would fix in iteration 6 — and are choosing not to because scope is controlled
Common mistakes
Bundling multiple changes into one prompt
→ "Fix the button, change the color, and add a header" in one prompt causes cascading changes that are hard to undo. One change per iteration, always.
Prioritizing visual polish over functionality
→ A beautiful app that does not work is worse than a plain app that works. Resolve all functional issues first, then one visual pass.