Before after

Produce honest, element-level evidence for a visible web change by composing existing agent-browser commands.

Read the capture protocol, the visual proof patterns, and the Vercel visual system completely before acting. Load the installed agent-browser core skill before running browser commands. Read GitHub publishing only when the user wants the proof shared on a GitHub issue or pull request.

Visual gate

Use this skill only when the changed behavior can be seen in a browser:

• Component layout, content, styling, or responsive changes.
• Loading, empty, error, validation, hover, focus, or interaction states.
• A visual regression fix that can be reproduced deterministically.

Do not use it merely because code changed. Use relevant tests for nonvisual work, performance-proof for measured performance claims, and explain-diff for code understanding. If the delta cannot be reproduced honestly, report the evidence gap instead of manufacturing a comparison.

Required proof basis

Before capturing, freeze: