Skip to content

Reviewing agent-built UI

A fixed order for checking interfaces a model built: foundations, then polish, then accessibility, then a headless screenshot pass.

  • Claude Code
  • Cursor

Order matters

Polish applied to a wrong layout gets thrown away with the layout. Run the passes in this order and stop when one finds structural problems.

Steps

  1. Foundations. Hierarchy, spacing, one primary action per view, container widths, line length. Report as Before / After / Why.
  2. Unslop. Subtract first, then sweep for generated-UI tells.
  3. Polish. Tabular numbers, named transition properties, press scale 0.96, hit areas, no layout shift on hover.
  4. Accessibility. Labels wired to inputs, real buttons, focus rings intact, 44px targets, reduced motion.
  5. Screenshot pass. Headless Chromium at 1440 and 390 wide, light and dark. Look at the images, not the DOM.
  6. Commit only when asked. The review is the deliverable; the fix is a separate decision.

Tooling

A local Playwright script with three arguments (url, output path, scroll offset) covers most of step 5. Keep it in a scratch folder outside the repo.