wowprompt

Design QA review of a built screen against the design file

Compares a built screen with its approved design and specification, lists every difference in spacing, type, colour, states, copy and behaviour, and sorts them by how much they matter so developers fix the right things before release. Use it in the last days of a sprint when a feature is built but not yet shipped.

A table of design differences with screen area, expected, actual and severity, a list of missing states, and a short release recommendation
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Feature and screen: [e.g. the checkout address step on the mobile web app]
  • Design specification: [paste or describe: spacing values, font sizes and weights, colours as tokens or hex codes, component names]
  • What was built: [paste notes, measurements from browser tools, or a description of screenshots]
  • States designed: [e.g. default, focus, error, loading, empty, disabled]
  • Breakpoints to check: [e.g. 360px, 768px, 1280px]
  • Copy approved: [paste the final text for labels, buttons and messages]
  • Release date: [date]

Task

Find every difference between the design and the build and decide what must be fixed before release.

Output format

  1. Verdict in two sentences: ready, ready with fixes, or not ready.
  2. | Area | Expected | Actual | Breakpoint | Severity: blocker, major, minor, polish |
  3. Missing or broken states, each with the steps to reach it.
  4. Copy differences: | Location | Approved text | Built text |
  5. Accessibility checks noticed during review: focus order, contrast, touch target size, labels on inputs.
  6. Fix list for developers in priority order, grouped by component.

Severity guide

  • Blocker: wrong behaviour, broken layout at a listed breakpoint, unreadable text, missing error state.
  • Major: wrong component, wrong colour token, copy that changes meaning.
  • Minor: spacing or size off by more than 4px, wrong font weight.
  • Polish: differences under 4px that nobody will notice in use.

Rules

  • Compare only against the specification given; where it is silent, say "not specified" instead of guessing.
  • Report each difference once, in the component where it starts.
  • Do not ask for pixel-perfect matches on polish items before a release date.
design qavisual qadesign reviewui bugspixel checkdesign to development

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity