ThinkWithPrompt by SynotticThinkWithPrompt

Check the built product against my design (design QA)

Gives you a structured design QA pass and a clear, prioritized bug list engineers can fix, from your notes on the build versus the spec.

Product & UX DesignRTFStandardSummarizeAnalyzeFill-in Template

The prompt

Help me run design QA on a feature that has been built. Feature and spec: [WHAT IT IS; PASTE OR SUMMARIZE THE SPEC - key screens, states, tokens, and copy] Build I am reviewing: [ENVIRONMENT, PLATFORM, BROWSERS/DEVICES] My observations so far: [PASTE NOTES ON DIFFERENCES I HAVE SPOTTED] Design system in use: [NAME OR "custom"] Release date: [WHEN IT SHIPS] First, give me a QA checklist tailored to this feature covering: layout and spacing at each breakpoint, typography and token use, color and contrast, component states (hover, focus, active, disabled, loading, error, empty), copy matches spec, interactions and motion, responsive behavior and long content, keyboard and screen reader basics, dark mode if supported. Then turn my observations into tickets. For each: a short title, where it is (screen, element, breakpoint), expected vs. actual, a severity (Blocker: breaks function or accessibility; Major: clearly off-spec and visible; Minor: small polish), and a suggested fix in design-system terms (e.g. "use spacing-400, not 20px"). Only file tickets for differences I report; do not guess at issues you cannot see. Return: the checklist, the ticket list sorted by severity, and a short note to the engineer that is appreciative and clear about what must be fixed before release vs. what can follow.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Product & UX Design prompts

What to fill in

  • ENVIRONMENT, PLATFORM, BROWSERS/DEVICES
  • PASTE NOTES ON DIFFERENCES I HAVE SPOTTED
  • NAME OR "custom"
  • WHEN IT SHIPS

How this prompt is built

This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.

Related prompts

Find more prompts like this