ui-review

combined

Retroactive 6-pillar visual audit of implemented frontend code Review UI code for design system compliance, accessibility, and best practices

When to use

Use this skill when you need review UI code for design system compliance, accessibility, and best practices.

When not to use

For accessibility-only issues → use `/ss-a11y`
For Nielsen UX heuristics → use `/ss-audit`
For a quick automated check → use `/ss-lint`
For non-UI code (data fetching, business rules)
Use this skill only when the task clearly matches its upstream source and local project context.
Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Conflict

The two copies describe different review procedures. The davepoon copy is a thin wrapper that delegates to an external workflow file and produces a 6-pillar graded audit (1-4 per pillar) in a UI-REVIEW.md file. The sickn33 copy is a self-contained checklist covering 8 specific areas (design tokens, component conventions, a11y, mobile, performance, typography, spacing, coherence) with a Pass/Needs Improvement/Fail output format. They overlap in the general goal of reviewing UI code, but the sickn33 copy contains material steps and constraints (specific checklists, output format, when-not-to-use guidance) that the davepoon copy lacks, and the davepoon copy has a different output artifact and grading scale. Crowning one would hide a real alternative procedure.