Iterate in small steps
Why surgical edits beat one giant "redo everything" prompt.
The instinct when a site isn’t quite right is to describe everything wrong with it in one big paragraph. Don’t. PageFork is much better at one change at a time than at ten changes at once.
Why small steps win
- Quality is higher. The AI focuses on one thing and does it well.
- Mistakes are easy to undo. One surgical change = one Undo to recover.
- You learn what works. If ten changes ship together and you only like seven, untangling them is painful.
- It’s cheaper in credits. Small prompts use fewer tokens. Several small prompts usually cost less than one giant prompt of equivalent scope.
The 1-2-3 loop
- Generate / edit.
- Review — what’s the single biggest thing still wrong?
- Fix that one thing, and go back to step 2.
Repeat until you run out of “biggest things”. Usually the whole loop is 4–8 turns for a solid result; sometimes more if you’re exploring.
A worked example
Starting from a generated site you don’t quite like:
Turn 1 — “The hero headline is too long. Shorten it to under 8 words, keep the sub-headline, keep the CTA button.”
Review. The headline is good, but the sub-headline now reads oddly next to it.
Turn 2 — “Rewrite the sub-headline to flow with the new headline. One sentence, plain, no jargon.”
Review. Copy is good. The hero still feels cramped.
Turn 3 — “Add more vertical breathing room in the hero. Larger padding top and bottom, larger gap between headline and sub-headline.”
Review. Layout is great. Colours feel off now.
Turn 4 — “The hero background is too bright. Make it darker and slightly warm, keep the lime CTA accent.”
Better result in 4 focused turns than in 1 kitchen-sink prompt.
Exceptions — when to combine
Combine multiple changes in one prompt only when they share the same intent:
- “Across every page, change the primary colour from blue to forest green.” One theme change, many places.
- “In the hero: darker background, shorter headline, punchier CTA text.” One emotional direction.
Combining unrelated changes (“rewrite the FAQ and change the pricing grid and add a footer”) is the anti-pattern.