Reviewing AI Code

An AI agent's world is text — it can't see what its code renders unless a tool hands it an image, and even then it needs to know what to look for.

A 12-Point Checklist for Verifying AI-Built UI

Twelve checks for what AI coding agents most reliably miss, why they miss each one, and the fastest way to trigger it to verify the fix.

The order that works: data shape, then boundaries, then logic. Top-to-bottom reading misses what AI-generated code gets wrong — and what to grep for.

How to review AI-generated code: what the agent already checked, what only you can catch, and a loop that closes the gap.

Plan and execute are easy to automate. Verification is where the quality is — and it's the one step an AI agent can't fully do by itself.

Good feedback to Claude Code names the location, the expectation, and the gap between them — most reports name only the gap, and the fix misses.

'The spacing looks off' gives an agent nothing to fix. Here's what to say instead, with a translation table of real vague-to-specific examples.