Fabricate keeps your conversation and codebase as context across every message. Follow-up prompts can be short, because the agent already knows what you’ve built so far.
The Iteration Loop
1
Look at the live preview
Click through the app. Find the single most important thing to change next.
2
Send one focused follow-up
Describe that one change clearly. Let it build and update the preview.
3
Check the result
Did it do what you expected? If yes, move to the next change. If not, refine.
4
Repeat
Each small, verified step compounds into a polished app.
Write Good Follow-Up Prompts
Follow-ups are where most of your prompting happens. The same rules apply as in Prompting Best Practices — be specific, change one thing — but with one addition: say what to keep, so the agent knows the boundary of the change.Fix One Thing at a Time
When something is broken or off, resist listing every problem in one message. Fixing issues one at a time makes it clear which fix worked and keeps changes isolated. Describe the problem concretely — what you did, what happened, what you expected:Discuss Before You Build
When a change is large or you’re unsure how to approach it, switch to Discuss Mode first. Discuss Mode is free — the agent can read your codebase and help you plan, but it won’t modify code. It’s the right place to think. A reliable pattern:1
Plan in Discuss Mode
“I want to add team workspaces where users invite others and assign roles. How should this be structured?”
2
Agree on an approach
Discuss the data model and the screens until the plan is clear.
3
Switch to Build Mode and execute
Build the agreed plan one feature at a time, using your follow-up prompts.
Use the Prompt Queue
While the agent is building, you don’t have to wait idle to line up your next instruction. The Prompt Queue lets you add follow-up messages that run in order, one after the other, as the agent finishes each task. The Prompt Queue is useful when:- You already know your next two or three changes and want to set them up in a row.
- You thought of a refinement while watching a build and want to capture it before you forget.
- You’re working through a clear checklist of small, independent tweaks.
Revert with Version History
Iteration is safe to experiment with because Fabricate keeps version history. Each build creates a snapshot, so if a change takes your app in the wrong direction, you can revert to an earlier snapshot and continue from there. Use version history when:- A change had unintended side effects and you’d rather start the step over.
- You preferred how the app worked a few messages ago.
- You want to try a bold change knowing you can roll it back.
1
Open version history
Find the version history panel for your project.
2
Pick an earlier snapshot
Browse back to a snapshot from before the change you want to undo.
3
Revert and keep going
Restore that snapshot, then send a new prompt to continue from the known-good state.
Knowing When to Stop
Iterate toward a clear goal, not forever. When the live preview does what you set out to build, you’re ready to publish. Polish is good; endless tweaking is not — ship it, get real feedback, and let that guide your next round of prompts.What’s Next?
Prompting Best Practices
The framework for writing prompts and follow-ups that work.
Discuss Mode
Plan changes for free before you build them.
Prompt Examples
Strong starter prompts grouped by app type.
Build Mode
How Build Mode turns each follow-up into code.