product-design-design-qa

Compares source designs against rendered implementations and produces prioritized fix lists before handoff.

634|124|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-design-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-design-design-qa
Source: https://github.com/AIDotNet/OpenCowork/tree/main/resources/extensions/product-design/skills/product-design-design-qa
Command: npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-design-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design implementations often drift from the source mockup in fonts, spacing, colors, and imagery, and these mismatches slip through when reviews rely on memory or code inspection alone. This Skill enforces an evidence-based visual QA pass that compares the actual source design against the actual rendered implementation before any build is handed off.

Core Features & Use Cases

  • Side-by-side visual comparison: Captures both the source design (Figma node, image, screenshot, mockup) and the rendered implementation (local URL, deployed URL, app screen) and judges differences from a combined comparison input at matched viewport and state.
  • Required fidelity surfaces: Always audits fonts/typography, spacing/layout rhythm, colors/tokens, image quality, and copy/content, flagging banned shortcuts like CSS art, inline SVG substitutes, or placeholder imagery replacing real assets.
  • Severity-ranked fix report: Produces a structured design-qa.md report with P0-P3 findings, evidence, concrete CSS/component fixes, an implementation checklist, and a final result of exactly passed or blocked.
  • Use Case: After building a prototype from a Figma frame, run this Skill to capture both artifacts, detect that the heading font weight and card padding drifted from the mock, and receive an ordered fix list before the build is marked done.

Quick Start

Run design QA comparing my Figma mockup against the local prototype at localhost:3000 and save the report as design-qa.md.

Frequently Asked Questions about product-design-design-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I QA a prototype against a Figma design before handoff?

Capture the Figma source and a screenshot of the rendered implementation at the same viewport and state, then compare them in a single combined input. The Skill audits typography, spacing, colors, imagery, and copy, then writes a design-qa.md report with severity-ranked findings and a passed or blocked result.

What does a design QA report check for visual fidelity?

Every report must evaluate five required surfaces: fonts and typography, spacing and layout rhythm, colors and tokens, image quality and asset fidelity, and copy/content. Findings are ranked P0 through P3 with evidence, impact, and concrete CSS or component fixes.

When should I use design QA instead of a design audit?

Use design QA only when both a source visual target and a rendered implementation exist to compare before handoff. Broad UX critique, product audits, and flow reviews without a source-to-implementation comparison should be routed to the audit skill instead.

Can a build pass design QA with only a full-page screenshot comparison?

No. A full-view comparison alone is insufficient when important details are not clearly readable. Focused region comparisons are required for precise typography, icons, controls, and dense UI, or the report must explain why they were not needed.

What causes a design QA run to be marked blocked?

A run is blocked when actionable P0, P1, or P2 findings remain, or when either the source design or the implementation cannot be opened, captured, or compared. The design-qa.md file must name the specific blocker and set final result to blocked.