Before you begin
Choose one user, one job, and one result. The first version should prove one complete workflow.
Use sample, synthetic, or de-identified information until you are ready to connect production data.
Build the first useful version
Your project is still exactly where you left it.
The last completed step was
the last completed step
The best next move is not to start over. Open the existing project and request one specific change.
A useful next prompt could be
“Review the current app and tell me the three smallest changes needed to make the main workflow
usable. Do not rebuild the app. Wait for me to choose one change.”
That keeps the current work intact and turns the next session into a short decision instead of
another blank canvas.
If something looked wrong in the preview, reply to this email with
1. What you expected
2. What happened instead
3. A screenshot, if helpful
We will help you find the next step.
Common mistakes
Rebuilding because you do not remember the last decision.
Giving a large rewrite instruction before reviewing the current state.
Assuming a confusing preview means all prior work is lost.
Frequently asked questions
Do I need to know how to code?
No. Describe the user, the job, the input, and the result. Technical users can add architecture details
later, but they are not required for the first workflow.
Should I connect real data immediately?
Not usually. Begin with representative sample, synthetic, or de-identified information, then connect
approved production sources after the workflow and controls are clear.