design-qa

Reviews rendered components and pages against design principles and fixes visual defects.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill design-qa-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-qa
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/design-qa
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill design-qa-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Visual defects like doubled seams, off-grid hairlines, inconsistent state treatments, and theme parity issues slip through code review because they only exist in rendered pixels. This Skill performs a rigorous visual QA pass over components, pages, or sweeps of several targets, judging the rendered output against design principles and fixing what has one right answer. ## Core Features & Use Cases - Rendered-pixel inspection: Captures every variant and state in both light and dark themes, magnifies joins, corners, dividers, and focus rings to find seam defects invisible at 1x. - Principle-based rubric: Judges arrangements against proximity, alignment, repetition, contrast, and spacing, plus component-scale craft checks for geometry, states, theme parity, and system fidelity. - Classified findings and fix loop: Labels each finding as Defect, Polish, or Direction, fixes defects and polish items at the source, re-renders before/after crops, and reports open taste calls with recommendations. - Use Case: After building a new React component in Storybook, run a design QA pass to catch a doubled border in its split variant, verify dark-mode parity, and compare it against sibling components before registration. ## Quick Start Ask the assistant to design QA the Button component and fix any visual defects it finds.

Frequently Asked Questions about design-qa

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

FAQPage Schema
How do I design QA a React component in Storybook?

Render every story variant in both light and dark themes, capture magnified crops of joins, corners, and focus rings, then drive hover, focus, disabled, and loading states for real. Compare the results against the design spec and the nearest sibling components before fixing defects at the source.

What visual defects does a design QA pass catch?

It catches doubled borders at shared edges, hairlines off the pixel grid, radii that break at nested corners, states that shift layout, and theme parity failures where dark mode dissolves a treatment. It also flags inconsistent state logic across sibling components.

Can I run a design QA sweep across multiple components at once?

Yes, a sweep reviews several components or pages individually and against each other, since cross-target inconsistency is the sweep's main purpose. Each target is judged on its own merits and then lined up against its nearest rendered relatives.

Why do colors look wrong in automated theme-switch screenshots?

After a programmatic theme flip in a hidden browser pane, CSS transitions can freeze mid-flight, so a token screenshots at neither theme's value. Let the page settle in a fronted tab or force-finish animations, and confirm suspicious colors with computed styles before reporting.

When is a clean design QA pass a valid outcome?

A clean pass is valid when the full coverage matrix was actually reviewed: all variants, states, themes, stress cases, and sibling comparisons. The report should state what was covered rather than inventing findings to justify the run.