design-review

Audits frontend views for design consistency, state coverage, accessibility, and anti-patterns.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill design-review-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/greglas75/zuvo/tree/main/skills/design-review
Command: npx skills add https://github.com/greglas75/zuvo --skill design-review-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend codebases drift over time: components duplicate, loading and error states go missing, accessibility attributes are skipped, and one-off implementations bypass the design system. This Skill runs a structured DX1-DX20 checklist audit across your views so inconsistencies and critical gaps are found systematically instead of by user complaint. ## Core Features & Use Cases - DX1-DX20 Code Audit: Scores each view on layout, design tokens, state coverage (loading/error/empty), keyboard navigation, ARIA, and shared component adoption, with critical gates for DX6/DX7/DX10/DX20. - DAP1-DAP12 Anti-Pattern Detection: Finds prop drilling, inline style overrides, missing confirmation dialogs, z-index wars, and missing reduced-motion support. - Visual & WCAG Mode: Optional chrome-devtools screenshots at three breakpoints plus axe-core accessibility scans when a dev server is running. - Auto-Fix & Loop Modes: --fix-critical repairs critical gate failures (loading.tsx/error.tsx creation, confirmation dialogs), and loop mode audits, fixes, and re-audits with a delta report. - Use Case: Run design-review src/app before a release to get per-view tier scores, a state coverage matrix, and a prioritized action plan saved to zuvo/audits/. ## Quick Start Ask the AI to run a design review audit on your frontend views, for example: audit the components in src/app for design consistency and accessibility.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I audit frontend components for design consistency?

Run the design-review skill against a directory or file, for example `design-review src/app`. It scores each view against the DX1-DX20 checklist covering tokens, states, accessibility, and shared component usage, then writes a report to zuvo/audits/.

What is the difference between design-review and a code audit?

design-review checks UI/UX concerns: state coverage, design tokens, ARIA, responsive behavior, and anti-patterns. Code quality issues belong to zuvo:code-audit and test quality to zuvo:test-audit, which are explicitly out of scope here.

Can design-review run accessibility scans with axe-core?

Yes, in visual mode with a running dev server and chrome-devtools tooling available. It captures screenshots at 1440, 768, and 375 widths and runs axe-core scans, which override grep-based DX15-DX17 scores.

Does design-review work with Next.js App Router projects?

Yes. It detects co-located loading.tsx and error.tsx files next to page.tsx, automatically scoring DX6 and DX7 as passing when boundaries exist, and its auto-fix can create these boundary files.

What does the --fix-critical flag change in my code?

It only touches the UI/states layer: adding loading wrappers, error boundaries, confirmation dialogs, and shared component imports for DX6, DX7, DX10, and DX20 failures. Business logic, data fetching, and event handlers are never modified.

When should I not use design-review?

Skip it for general code quality or test quality audits, and when you need to create new designs rather than audit existing ones. For qualitative multi-agent review of a component, use zuvo:ui-design-team instead.