A useful critique connects a visible problem to a task someone is trying to finish. Start with the goal, then ask for evidence. A screenshot alone cannot prove that a control works or that a page is accessible.
Copy the prompt
Review this interface for clarity and usability.
Audience: [who uses it]
Primary task: [what they need to finish]
Context: [screen, screenshot, or URL available to you]
Constraints: [what must stay unchanged]
First, explain the main action a new visitor is likely to notice.
Then identify up to five issues that interfere with the primary task.
For each issue, give:
- The exact element or state you inspected.
- The user problem and the evidence for it.
- The smallest useful improvement.
- How to verify that improvement.
Separate observed facts from assumptions. Do not invent user research.
If you only have a screenshot, mark behavior, keyboard access, contrast,
and responsive layouts as unverified unless you can actually test them.
End with the single change you would make first and why.
Give it useful context
Replace the brackets before you run the prompt. Include the action the screen should support, any existing design rules, and what you cannot change. Avoid including customer records, access tokens, or private screenshots without permission.
Check the feedback
Prefer findings you can point to on the screen. “This feels dated” is a preference; “the primary action is visually weaker than three secondary actions” is a testable observation. Verify suggested changes on the real interface before treating them as improvements.
Adapt it
For an existing product, add a requirement to preserve established labels and interactions. For a first concept, ask for the three most important unanswered questions before visual polish.
