Review ux fix

Skill cloverink/shipwright/skills/review-ux-fix

Production-grade Claude Code skills for shipping quality code. One command takes your branch from "done coding" to PR-ready via audit → review → docs → push.

Install

npx -y skills add cloverink/shipwright --skill review-ux-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Automated UX review → fix → re-review loop. Target is perfection (10/10). Fixes ALL severities including Suggestions — because UX polish compounds.

SKILL.md

2.1 KB, as published. Nobody here has run it

/review-ux-fix

Iterative UX review-fix loop targeting perfection. Unlike /review-code-fix, this fixes every issue including Suggestions.

When to use: UX-only polish (CSS, spacing, micro-interactions) with no code logic changes. Use /review-full instead if: your diff has logic/API changes too — it'll run code review alongside. Called by: /review-full (auto-dispatched on frontend diffs — /ship Phase R reaches this transitively).

How it works

Round 1: UX review → list issues → fix ALL severities → re-review
Round 2: Review again → fix remaining → re-review
Round 3: Final attempt → fix → final review
         If still failing → report to user

Score Gate

Target is exactly 10/10. Any issue at any severity fails the gate.

Why perfection? UX issues compound. A slightly off button, a missing loading state, and a wonky mobile layout individually seem minor — together they make the product feel unpolished.

Why fix Suggestions too?

Code Suggestions are style preferences — reasonable people disagree. UX Suggestions are polish items — spacing, alignment, micro-interactions — that users feel. Fix them all.

Review Categories

Design system compliance — tokens, typography, spacing
Visual polish — alignment, consistency, whitespace rhythm
Responsive behavior — mobile, tablet, desktop
Loading states — skeleton/shimmer for async content
Error states — user-friendly messages, retry options
Empty states — helpful messaging when no data exists

Relationship to /review-code-fix

Complementary, not overlapping:

/review-code-fix — correctness (types, security, performance, tests)
/review-ux-fix — experience (design, responsiveness, states, polish)