gate
Run the one-command quality gate and report the real N/N result. Use before claiming any build/review is done.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/plugin87/ux-ui-agent-skills/HEAD/.claude/commands/gate.md -o ~/.claude/commands/gate.mdgate.md
Run the full quality gate and report the ACTUAL output — never a remembered or
reasoned number.
1. Run: `node scripts/accuracy_report.mjs`
(tokens + contrast + spec + no-hardcode + theme-refs + no-emoji +
real-render WCAG + state-aware, light and dark — all-or-nothing).
2. Report the exact `N/N` line it prints.
3. If it is not fully green:
- List each failing check verbatim.
- Fix the cause (do not suppress the check).
- Re-run until green. Do not announce success between failures.
4. For any rendered HTML touched this session, also run the pixel-truth checks
the gate cannot prove:
- `node scripts/verify_states.mjs <file> [--dark]`
- `node scripts/verify_responsive.mjs <file>`
- RENDER-AND-LOOK: screenshot the harness, park the pointer off it, inspect
every state, click each control to confirm the state changed.
Honest scope: these gates prove objective correctness (tokens, a11y, no drift).
They do not prove taste. Pair with `node scripts/taste_audit.mjs` + human review;
never claim auto-100% on aesthetics.Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.
Apply a visual direction — an archetype (high-end agency, editorial minimal, brutalist, soft-SaaS, dark-tech) or one of 138 named design systems (apple, linear-app, stripe, vercel, notion, material, shadcn, spotify, tesla…) — by resolving it into the token system. Use when the user wants a specific look/vibe/brand feel, or asks to make a design feel premium/expensive/non-generic.
Generate a complete, accessible brand design system from a brief — primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css — verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.
Generate production-ready, accessible, token-driven component code for ANY framework — React+Tailwind, Next.js, SwiftUI, Vue, Svelte, Angular, Solid, Web Components/Lit, React Native, Flutter, Jetpack Compose, vanilla CSS, or CSS-in-JS. Use when the user wants working UI code for a component or screen in a specific stack.
Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, token mapping, and accessibility. Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework code, use design-code.
Set up or run design QA gates — 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.
Review or audit a design/UI across 6 weighted dimensions with Nielsen's 10 heuristics and a prioritized findings table. Use when the user wants a design critique, quality score, heuristic evaluation, or audit of an existing screen, page, or product before/after build.
Generate, extend, or audit design tokens in DTCG format with the 3-tier architecture (primitive → semantic → component). Use when the user wants a color palette, type scale, spacing/shadow/radius/motion tokens, multi-brand theming, or wants to validate token files. Covers colors, typography, spacing, shadows, borders, breakpoints, motion, gradients, opacity, blur, sizing, states, theming.