What problem does it solve? Design quality regresses silently when teams ship components without automated gates — hardcoded hex values creep in, contrast fails WCAG, and accessibility issues reach production. This Skill establishes the full QA pyramid so every PR is blocked from introducing token, contrast, a11y, or visual regressions. ## Core Features & Use Cases - Fast CI Gates: Run token validation, batch WCAG contrast checks over token pairs, and hardcoded-value linting (no raw hex/px/timing) on every commit or pull request. - Automated Accessibility: Integrate axe-core or Pa11y across component states (error, loading, disabled, expanded, selected) with zero serious/critical violations allowed to merge, plus a real-render contrast gate using headless Chromium that measures computed-style, alpha-composited contrast. - Visual Regression & Manual Sign-off: Snapshot components across variants, sizes, states, light/dark themes, breakpoints, and RTL with frozen animations, then complete the manual a11y checklist (keyboard, screen reader, 400% reflow, 200% text-spacing, reduced-motion, forced-colors) per release. - Use Case: Before shipping a new component library, wire these gates into your CI workflow so an unreviewed PR cannot introduce an unresolved token alias, contrast failure, raw hex value, or axe violation. ## Quick Start Set up the design QA gates for my component library and run the token, contrast, and hardcoded-value checks on the current source directory.