ux-review

Audit UX specs for completeness, accessibility, and platform conventions.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill ux-review-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/ux-review
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill ux-review-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catches gaps in UX specs by performing a fresh-eyes audit for completeness, accessibility (WCAG 2.2 AA), and platform-convention compliance, helping teams hand off reliable designs to engineers.

Core Features & Use Cases

  • Fresh-session UX review to verify header sections, state coverage, token references, and accessibility notes.
  • Cross-checks against platform conventions (iOS HIG / Material 3) and token usage to ensure consistency.
  • Outputs a verdict (APPROVED / NEEDS REVISION / MAJOR REVISION) with blockers for the engineers and designers to address in PRDs.

Quick Start

Run the ux-review tool on your UX spec file to generate a verdict and actionable blockers.

Frequently Asked Questions about ux-review

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

FAQPage Schema
How do I audit a UX spec for completeness before engineering handoff?

Auditing a UX spec for completeness involves checking header sections, state coverage, token references, and accessibility notes in a fresh session. This generates an implementation readiness verdict with actionable blockers to resolve before engineering begins.

How do I check my UX design for WCAG 2.2 AA accessibility compliance?

Checking UX design for WCAG 2.2 AA compliance involves auditing the spec's accessibility notes and state coverage against platform conventions. This yields a verdict with specific blockers to fix accessibility gaps before engineers start implementation.

Does UX spec verification support both iOS HIG and Material 3 platform conventions?

UX spec verification supports both iOS HIG and Material 3 conventions. The audit cross-checks design specs against these platform guidelines and token usage to ensure consistency, generating blockers for any identified convention violations.

What is the best way to validate implementation readiness for a UX specification?

Validating implementation readiness requires a fresh-session audit checking completeness, accessibility, and platform conventions. This generates an APPROVED or NEEDS REVISION verdict along with a review snapshot file for the engineering team.

Why should I run a UX review in a fresh session instead of my design environment?

Running a UX review in a fresh session prevents authoring context leakage, ensuring an objective audit. This approach avoids unconscious bias from the design phase to deliver a true fresh-eyes validation of spec completeness and accessibility.

What does a UX spec review verdict output include for the engineering team?

A UX spec review verdict outputs an APPROVED, NEEDS REVISION, or MAJOR REVISION status alongside specific blockers. It optionally generates a review.md snapshot file detailing the gaps engineers and designers must address in the PRD.