AI / Design Communication & Image Prompting

UI Design Review

Find usability problems instead of debating whether it looks good

Here is my UI design description: [description]. Review it from a usability perspective and list the problems: 1) Is the information hierarchy clear — what does the user see first? 2) Can the primary action be found easily? 3) Where does the user have to recall or guess? 4) How should the empty, error, and loading states each be designed? Do not comment on whether the color scheme looks good.

How to use

Describe the screen as a user meets it, not as a feature list — otherwise the review grades your intent rather than the screen.

Good for

The screen already works but you cannot say why users get stuck — the four questions (hierarchy, primary action, recall burden, three states) pin the problem to a specific control and position instead of more visual tweaking.
You need a problem list free of personal taste before a review meeting — run the fixed four questions first so the meeting discusses facts rather than 'I don't like how it looks'.

Not for

You have one sentence of feature description and no real screen, field list, or screenshot — the model reviews generic best practice, which grades a template, not your interface.
You need to judge brand direction (is it expensive enough, does it match the tone) — usability review cannot answer that; use a visual brief or brand principles instead.

Example

Input

Settings page: avatar and nickname at top, 14 toggles laid out flat with no grouping, a grey 'Save' button at the bottom, and edits are lost if you don't press it

What you get

Names the hierarchy problem (14 ungrouped toggles, no visual priority), the primary-action risk (a grey Save button reads as disabled, and there is no autosave), and the recall burden (users must remember what they changed). Adds the missing three states: offline should grey out the toggles and say why. Ranks by 'loses data > can't be found > must be remembered' rather than top-to-bottom page order.

Common mistakes

Sending a feature list as the interface description ('it has search, filters, favourites') — the review can only grade the list, never the control, its position, or its state.
Also asking it to 'give me a nicer redesign while you're at it' — visual preference contaminates the usability findings and the list turns into a taste vote.

Try tweaking it like this

Change 'do not comment on color' to 'you may comment on whether contrast reaches 4.5:1' — one verifiable visual standard stays in, and the rest is still not about beauty.
Append 'tag each issue with how many seconds it costs the user and whether they would give up' — the list becomes scheduling input on the spot.