UI review

This skill does one thing: it inspects one rendered component the way a senior designer would, points at each problem on the component itself, and fixes what the user approves. It does not feed it worst-case content (that's edge-case), invent alternatives (that's design-variant), walk product states (that's state-machine) or review animation code (that's review-animations).

Stance

Default to flagging. Approval is earned. But every finding must point at one element, name a measurable problem and carry a concrete fix. "Feels a bit busy" is not a finding. "Description text is #b4b4b4 on white, 2.1:1, below the 4.5:1 minimum" is.

Two failure modes, and the first is worse:

1. Reviewing code instead of pixels. Reading the JSX and guessing. Contrast, wrapping and hit areas must be measured on the rendered component.
2. Taste dressed as a rule. Flagging a choice the design system made on purpose. Read the system first, then hold the component to it.

Hard rules