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
The same task becomes a different product depending on who performs it.
“Review a contract” could mean:
A lawyer
Needs clauses, risks, citations, and a defensible audit trail.
A salesperson
Needs unusual terms, approval requirements, and a simple next step.
A customer
Needs a plain-language explanation and a way to ask a question.
An operations manager
Needs extracted fields, exceptions, and a status that moves through a workflow.
Add one sentence to your project
“The primary user is [role]. They use this app when [specific situation].”
Then add
“They should be able to finish without [current frustration or manual step].”
That gives Empromptu AI a practical basis for navigation, permissions, wording, and output design.
Common mistakes
Using “admin” or “customer” when there are materially different roles.
Ignoring what information the user can see or change.
Designing the screen before defining the user’s job.
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.