ui-ux-team

Use the /review command with screenshots, a prototype, or a live UI. Findings are returned with severity levels (critical, major, moderate, minor), user impact, evidence, and a concrete fix for each issue, ordered by severity.

Use the /audit command, which applies a WCAG 2.2 Level AA checklist organized by the POUR principles, including the nine criteria new in 2.2 such as target size, focus appearance, and redundant entry. It separates what screenshots can verify from what needs keyboard or assistive-technology testing.

/design creates a new screen or feature from scratch following the full working method. /revise applies specific feedback while preserving sound existing decisions. /revamp systematically reworks a weak experience, stating what stays, what changes, and why, without defaulting to a full redesign.

Yes, the Skill is written for stacks using Next.js, Tailwind, and shadcn/ui on Radix primitives. It reuses existing components and tokens before proposing new ones and checks what is already installed before suggesting additions.

Yes, the anti-patterns reference covers the full dark-pattern taxonomy including roach motel, confirmshaming, hidden costs, forced continuity, and preselection, with the ethical alternative for each. Dark patterns are treated as critical findings regardless of conversion goals.

It does not replace product requirement definition, which belongs to product-team, or code implementation, which belongs to dev-team. It also does not invent research or user data; if evidence is missing, it states that rather than asserting findings.