Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: design-qadescription: Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.
Skill: Design QA
Step 0: is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING
On KIT_MISSING only the skill folders were installed, which is what
npx skills add does. Say so plainly, point the user at
npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the
contents of a file you could not open.
Stand up the automated + manual gates that stop quality from regressing.
Wire the fast gates first (every commit/PR): python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py, python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.py (batch WCAG over the token pairs), and python3 ${CLAUDE_SKILL_DIR}/../../../scripts/lint_hardcodes.py <src> (no raw hex/px/timing in component code). The repo's .github/workflows/ci.yml runs these.
Add automated a11y (axe-core / Pa11y) over each component's states (error/loading/disabled/expanded/selected), zero serious/critical to merge. Run the real-render contrast gatenode ${CLAUDE_SKILL_DIR}/../../../scripts/gate.mjs measure_render.mjs <file.html> (and --dark). It opens the page in headless Chromium, disables transitions, and measures the true computed-style + alpha-composited contrast of every text element (catches what static token checks miss).