Before you begin
Open the existing project so your instruction is grounded in the current app.
Write the instruction from the user’s perspective, then state the exact result you want to inspect.
Write the instruction
When one prompt changes navigation, data, permissions, AI behavior, and visual design at the same time, it becomes hard to know which change caused a problem.
Use a controlled sequence
1. State what must remain unchanged.
2. Name one part of the system.
3. Describe the exact new behavior.
4. Define how you will know it worked.
Example
“Keep the current upload and results workflow unchanged. Only change the review screen. Add an approval status with options for approved, needs changes, and rejected. A reviewer must choose a status before submitting.”
After that works, make the next change.
Small prompts are not slower. They reduce rework, preserve working code, and give you a clear point to roll back to if the result is wrong.
Common mistakes
Combining visual, data, workflow, and integration changes in one prompt.
Letting a focused edit become an uncontrolled rewrite.
Failing to preserve a working version before a large change.
Frequently asked questions
How long should a prompt be?
Long enough to define the user, job, input, rules, output, and important constraints. Clear structure matters more than word count.
Can I make several changes in one prompt?
Small related changes can be combined, but changes to different systems are easier to test and recover when requested separately.