version: "1.0.0" name: design-qa description: "Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit."

Design QA

Use this internal helper to compare a prototype's source design against the rendered implementation before handoff.

Do not use this skill for broad UX critique, design critique, product audits, or flow reviews. Use audit for those user-facing requests.

Use this skill before every Product Design build handoff.

A passing QA run requires both:

• a source visual target: Figma node, image, screenshot, mockup, or source capture
• a rendered implementation: local URL, deployed URL, app screen, component, or screenshot

If either artifact cannot be opened, captured, or compared, write design-qa.md with final result: blocked and name the blocker. Do not let the build skill hand off as done.

Critical Overrides

Follow critical-overrides.

Workflow

Compare the intended design to the implementation as a product-quality reviewer, not as a generic aesthetic critic. The output must be a prioritized fix list grounded in evidence from both artifacts.

Do not write the QA review from memory, code, or file paths alone. Open or capture both the source design and the implementation first, then compare what is actually visible.

Do not pretend separate image views are side-by-side comparison. Put the source image and the implementation screenshot together in the same comparison input, then judge the visible differences from that combined input.

1. Identify the comparison target.

• Determine the source design: Figma node, image, design board, screenshot, spec, or mockup.
• Determine the implementation: local URL, deployed URL, app screen, component, screenshot, or code-rendered view.
• Match the same viewport, state, theme, device density, route, content, auth state, and interaction state before judging.
• If artifacts do not represent the same state, call that out first and avoid false precision.

1. Capture evidence.

• For Figma, use design context and screenshot tools when available.
• For web/app implementations, open the target in a browser and capture screenshots at the intended viewport.
• Capture additional states when relevant: mobile/desktop, hover/focus/active, empty/loading/error, dark/light, and key responsive breakpoints.
• Save paths or URLs for screenshots when available so findings can cite evidence.
• Capturing screenshots is not enough. Put the source image and the implementation screenshot together in the same comparison input before judging.

1. Normalize before comparing.

• Align crop, viewport size, scale, and device frame. Do not compare a framed mockup to an unframed page without noting the mismatch.
• Prefer comparing content regions over full browser chrome or surrounding canvas.

1. Compare at the right level of detail.

• Use a full-view comparison to judge overall composition, hierarchy, layout, density, and responsive structure.
• Use focused region comparisons when important details are too small to judge in the full-view comparison.
• Choose focused regions from the actual source and implementation. Use them where fidelity depends on precise typography, alignment, imagery, assets, icons, logos, controls, forms, navigation, tables, dense UI, or visible interaction states.
• If no focused region is needed, say why in design-qa.md.
• Do not pass QA from a full-view comparison alone when important details are not clearly readable.

1. Review systematically.

• Read qa-rubric when the QA pass spans more than a quick visual check.
• Check information architecture, layout, spacing, typography/fonts, color, imagery/image quality, icons, copy, affordances, interaction states, responsiveness, accessibility, and polish.
• Always make a specific pass over the five required fidelity surfaces: fonts/typography, spacing/layout rhythm, colors/tokens, image quality, and copy/content. Do this even if the user did not name those areas explicitly.
• If the mock does not address some issue you're seeing (e.g. a null state), call that out as a separate finding as a shortcoming of the mock to be addressed.
• Your other goal is to decide whether the implementation "looks as good" as the mock. If there are stylistic problems, call them out. If the user's prompt is leaking into the implementation (vs letting the app stand on its own), call that out as well.
• Distinguish design drift from intentional product/code constraints. If a deviation may be intentional, phrase it as a question or assumption.

1. Produce a fix-oriented QA report.

• Lead with findings, ordered by severity and user impact.
• For each finding include: severity, location, what differs, evidence, why it matters, and the concrete fix.
• Include exact CSS/component/token suggestions when the implementation context is available.
• Separate objective mismatches from subjective polish recommendations.
• Do not say a design matches, is done, or is as good as it can get until the required fidelity surfaces have been checked and any remaining differences are explicitly classified as acceptable, expected, or still actionable.
• End with a concise implementation checklist.

Required Fidelity Surfaces

Every QA report must explicitly evaluate these surfaces:

• Fonts and typography: family, fallback, weight, size, line height, letter spacing, antialiasing, hierarchy, wrapping, truncation, and whether display text and small UI text use appropriate optical weights. It is incredibly important to check fonts carefully for fidelity, including looking up similar typefaces or using image analysis to find the font differences.
• Spacing and layout rhythm: frame size, crop, alignment, margins, padding, grid tracks, section gaps, component spacing, radii, shadows/elevation, and vertical rhythm.
• Colors and visual tokens: sampled or inferred palette, gradients, opacity, contrast, semantic state colors, foreground/background balance, and whether CSS tokens map to the source design.
• Image quality and asset fidelity: subject correctness, crop, scale, sharpness, compression, transparency halos, masking, background treatment, raster-vs-vector appropriateness, and whether generated assets match the source art direction. Fail QA if logos, illustrations, decorative marks, product imagery, non-standard icons, or other visible image assets from the visual target were replaced with custom inline SVG, handcrafted SVG, HTML elements, div/span shapes, CSS drawings, gradients, emoji, text glyphs, placeholder shapes, or code-native approximations.
• Copy and content of app-specific text

Severity

• P0: Blocks core use, severe accessibility failure, broken layout, or impossible task.
• P1: Major design mismatch or usability regression likely to be noticed by users.
• P2: Moderate visual drift, inconsistent state, responsive issue, or fixable polish gap.
• P3: Minor refinement that improves fidelity but does not block acceptance.

Output Format

Use this structure unless the user asks otherwise:

**Findings**
-[P1] Short issue title
  Location: screen/component/selector/file if known.
  Evidence: design does X, implementation does Y.
  Impact: why this matters.
  Fix: concrete change.
 
**Open Questions**
-Any ambiguity about intentional deviations, unavailable states, or missing artifacts.
 
**Implementation Checklist**
-Ordered fixes that can be executed directly.
 
**Follow-up Polish**
-P3 refinements that can improve fidelity after handoff.

If there are no substantive mismatches, say that clearly and list any residual test gaps.

When this skill is used before handoff, save the latest QA report as project-root design-qa.md.

design-qa.md must include:

• source visual truth path
• implementation screenshot path
• viewport
• state
• full-view comparison evidence
• focused region comparison evidence, or why it was not needed
• findings
• patches made since the previous QA pass
• final result

final result must be exactly passed or blocked.

Use passed when there are no actionable P0/P1/P2 findings. P3 findings may remain as follow-up polish. Use blocked when actionable P0/P1/P2 findings remain and name the blocker.

Return the file path with the QA report.