Review UI

The one rule: a visual claim is settled by rendering, never by inference. A careful read of a style diff produces hypotheses — "these two classes may collide", "this might overflow at phone width", "this pair looks low-contrast" — and a hypothesis reported as a finding is a guess wearing evidence's clothing. This skill turns each one into a verdict with a screenshot behind it.

0. Scope the surfaces

From the range: git diff <base>...HEAD --name-only, keep the files a browser renders (HTML, CSS/styling, JSX/TSX/Vue/Svelte components, templates). None → report no rendered surface and stop. Map each kept file to the screen(s) or route(s) where its change shows. Done when: every changed rendered file has a named screen.

1. Get it running — live first