How to run a visual review with Claude Code (step by step)
One-click setup and a 30-second loop: connect Walkie, record while you talk and point, hand the bundle to Claude Code, verify the fix.
Reviewing AI CodeWhy your AI agent can't see what it built
An agent works in text and sees a render only when a tool hands it one. What Claude Code can and cannot see in 2026, and what each look costs in tokens.
Reviewing AI CodeA 12-Point Checklist for Verifying AI-Built UI
Twelve checks for the states AI coding agents most reliably miss, why each one gets missed, and the fastest way to force it to appear right now.
Reviewing AI CodeHow to review AI-generated code you didn't write
Read a generated diff in one order: data shape, then boundaries, then logic. Five failure patterns with the exact strings to grep for, and how deep to go.
Reviewing AI CodeHow to review what your AI coding agent built
What the agent already checked, what only you can catch, and a plan-execute-verify loop that closes the gap — with the token cost of every way of looking.
Reviewing AI CodeThe plan → execute → verify loop, explained
Plan and execute are easy to automate. Verification is where quality lives — and the one step an AI coding agent can only close if you hand it a check.
Reviewing AI CodeHow to Give Feedback to Claude Code That Lands
Feedback lands when it names the location, the expectation, and the gap. Most reports name only the gap. Plus the Claude Code files that make it stick.
Reviewing AI CodeHow to describe a visual bug to an AI coding agent
The spacing looks off gives an agent nothing to fix. What to say instead: a ten-row translation table and the three bug types words alone cannot carry.