Design & UX
Asking a model "what do you think of this design?" gets you a list of compliments and a suggestion to add more whitespace. The prompts below are written to stop that. They force a verdict, make the critique point at a named element on the screen, separate genuine problems from matters of taste, and insist that copy which is already fine gets left alone. Use them on a screen before design review, on microcopy you wrote as a placeholder and never revisited, on a flow where only the happy path exists, or on a request that arrived as one vague sentence and needs to become a spec.
36 prompts in 5 groups
Design & UX21 categories
Interface copy
Every word inside the product: button labels, error messages, empty states and what things are called.
- Rewrite the microcopy on this screenLongBefore shipping a screen where the words started as placeholders you never revisited.
- Pick the right words for this buttonLongWhen the options are "OK / Cancel" and nobody is sure what OK does.
- Design the empty state for this screenLongThe screen looks great with data and blank the first time anyone opens it.
- Rewrite these error messages for humansLongYour UI says "An error occurred" and support is fielding the fallout.
- Name this thing in the interfaceLongNaming a feature, tab, or object that users will have to learn and repeat.
- A better label for this buttonShortWhen the options are "OK" and "Cancel" and nobody is sure what OK does.
- Halve the words on this screenShortInterface copy that grew one clause at a time through review.
- Name this stateShortLabelling a status, tab or filter people have to recognise at a glance.
- Write the empty stateShortThe screen looks great full of data and blank the first time anyone opens it.
- Alternatives to this wordShortA term that starts the same argument in every design review.
- Rewrite these error messagesMediumYour interface says "An error occurred" and support is fielding the fallout.
Critique and review
Passes over a finished screen: design critique, heuristics, accessibility and contrast checks.
- Critique this screen like a design leadLongBefore design review, when you want the criticism early and privately.
- Accessibility review of this interfaceLongAny screen going to real users, especially forms and custom controls.
- Check this palette for contrast and colour useLongBefore a palette gets used across a hundred components and becomes permanent.
- Run a heuristic evaluation on this interfaceLongYou need structured findings fast and there is no time for user testing.
- Is this clear without context?ShortA screen that makes sense to you because you have been staring at it for a week.
- Quick accessibility checkShortA custom control you built yourself and have never tried without a mouse.
- What is confusing here?ShortWhen something about a screen feels off and you cannot name it.
- Critique this screen in five linesMediumA fast private critique before the design review, with no room for padding.
- Is this a real problem or just my taste?MediumBefore sending design feedback that might be preference dressed as principle.
Flows and forms
Whole journeys rather than single screens: onboarding, missing states, and forms field by field.
- Critique this onboarding flowLongSign-ups are healthy and activation is not.
- Review this form field by fieldLongAny form with more than three fields, before it goes anywhere near users.
- Find the gaps in this user flowLongThe happy path is designed and nothing else is.
- What would a first-timer miss?ShortBefore shipping something to people who have never seen it before.
- Which states does this flow not handle?MediumThe happy path is designed and nothing else is.
- Tighten this formMediumAny form that has quietly gained a field per quarter.
Briefs and decisions
The work around the design: turning a request into a brief, choosing between options, writing down why.
- Write up the rationale for this design decisionLongDocumenting a decision before everyone forgets why it was made.
- Compare two design options and pick oneLongTwo mockups, a stalled debate, and a decision due today.
- Turn this request into a design briefLongStarting work where the whole goal arrived as one Slack message.
- Turn research notes into insightsLongYou have a pile of interview notes and a deadline to say what they mean.
- Turn a vague request into a design specLongSomeone asked for "a dashboard" and then walked away.
Got one that isn't here?
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt