Skip to main content
skill CX Codex

design-qa · plugin87 — Claude Code skill: design checks and installation

This skill sets up checks for tokens, contrast, accessibility, and visual regressions. Use it to QA a component or screen before release.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add plugin87/ux-ui-agent-skills --skill design-qa -a claude-code
Open on GitHub

What design-qa does

design-qa helps build a UI QA workflow covering token and hardcoded-value linting, automated accessibility checks with axe-core or Pa11y, contrast, and visual snapshots. The checks can cover component states, light and dark themes, RTL, and key breakpoints. A manual accessibility checklist is included for release sign-off.

The skill relies on files from the kit. Its checks include Python scripts for tokens, contrast, and hardcoded values, plus gate.mjs, which opens a page in headless Chromium and measures contrast on rendered text. Installing only the skill folder is not enough: if the tokens directory is missing, stop and install the kit with npx ux-ui-agent-skills init or install the plugin. Without the kit files, the checks cannot read the required data.

What it helps with

  • lint tokens and hardcoded values in component code
  • detect contrast failures in rendered UI
  • check component states with axe-core or Pa11y
  • compare visual snapshots across themes, variants, and RTL
  • complete a manual accessibility review before release

Example prompts for the agent

  • Set up design checks for this project and add the fast gates to CI.
  • Check every state of this component with axe-core or Pa11y.
  • Capture visual snapshots of the components in dark mode and RTL.

How to install design-qa

1Skills CLI (Vercel)

npx skills add plugin87/ux-ui-agent-skills --skill design-qa -a claude-code

2Manually: put the files in place

~/.claude/skills/design-qa/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/design-qa/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about design-qa

How do I install design-qa in Claude Code?

Run npx skills add plugin87/ux-ui-agent-skills --skill design-qa -a claude-code. The skill file is at ~/.claude/skills/design-qa/SKILL.md.

What does design-qa do?

It helps set up automated and manual UI checks for tokens, contrast, accessibility, visual regressions, and release sign-off.

What does design-qa need to run?

It relies on kit files, including the tokens directory. If you installed only the skill folder, run npx ux-ui-agent-skills init or install the plugin first.

Source text

SKILL.md · MIT
---
name: design-qa
description: 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.

## Steps
1. Read `${CLAUDE_SKILL_DIR}/../../../workflows/design-qa.md` (the QA pyramid: token/lint gates → automated a11y → visual regression → manual a11y).
2. 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.
3. 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 gate** `node ${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).
4. Add **visual regression** snapshots across variants × sizes × states × light/dark + key breakpoints + RTL; freeze animations + deterministic data.
5. Sign off the **manual a11y** checklist per release (keyboard, screen reader, 400% reflow, 200% text-spacing, reduced-motion, forced-colors; `${CLAUDE_SKILL_DIR}/../../../accessibility/*`).

## Verification (definition of done)
- An unreviewed PR cannot introduce an unresolved token alias, a contrast failure, a raw hex/px, or an axe violation: a gate blocks each.
- Snapshots cover dark mode + RTL + the semantic-changing states, not just the happy path.
- Manual a11y checklist signed off for the release.

© plugin87 · MIT · plugin87/ux-ui-agent-skills

Similar skills

Everything for Design →

design-qa by other authors comes first.

From the same set16

apply-aesthetic Picks a visual direction — an archetype or a named design system — and resolves it into your project's tokens. Useful when you want a specific look, not whatever the agent improvises. CX Codex +1 529installs design-code This skill generates component and screen code for a requested framework. Use it when you need token-based UI with accessibility checks. CX Codex +1 525installs design-component Produces UI component specifications covering anatomy, 8 interactive states, tokens, and accessibility. Useful when designing components in a design system before coding. CX Codex +1 522installs ux-writing Write or review interface text, from button labels to errors and empty states. The skill applies a project’s voice and checks copy against a pre-ship checklist. CX Codex +1 517installs brandkit Build a token-based design foundation from a product brief, with separate light and dark themes and contrast checks. Use it to establish shared visual rules before designing screens. CX Codex +1 510installs migrate-design-system Maps your design tokens to another system and back: Material 3, Apple HIG, Fluent 2, shadcn/ui, Radix. Useful when you borrow a look or move onto a new stack. CX Codex +1 487installs prototype Guides interface design across a five-tier fidelity ladder from content to code. It helps map user flows, build wireframes, and draft usability test plans. CX Codex +1 484installs token-build Generate web and mobile theme files from DTCG JSON tokens, or wire the build into CI. Useful when one token source needs outputs for several platforms. CX Codex +1 480installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor