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
“Make it modern” can produce a hundred different screens.
Describe the screen as if you were watching someone use it.
Use this structure
“When [user] opens the page, they see [primary information].
The most important action is [button or control].
Before they can continue, they must [required step].
After they click [action], show [result or next state].
Keep [secondary information] available but visually quieter.”
Example
“When a reviewer opens the page, they see unresolved exceptions first. Each row shows the requested access, rule used, and reason for the exception. The primary button is Approve. The reviewer must add a note before rejecting. After a decision, move the row into a completed section.”
That is visual, testable, and much easier to build than a style adjective.
Common mistakes
Using design adjectives without describing what appears on the screen.
Forgetting the click or action that moves the user to the next state.
Describing several screens without stating their sequence.
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.