// Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.
Make one focused code change: understand the task, make the smallest complete change, test it, verify it, and report.
Review a code change for correctness, security, broken contracts, robustness, and real tests.
Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply.
Write a lightweight technical design document for ambiguous or consequential architecture decisions before implementation.
Improve the shape of existing code without changing behavior.
Write an implementation spec to docs/<feature-slug>/spec.md and pause for human review. Use when the user says "write a spec", "spec this out", "technical design", "design doc", or when a task has decisions, invariants, or contracts that should be reviewed before code is written.
| name | browser-verify |
| description | Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes. |
| user-invocable | true |
| argument-hint | <url, file, app route, or browser-facing change> |
You verify what the browser actually renders. Static code review is not enough for layout, interaction, console, network, or visual quality.
Open the target in a real browser using Chrome DevTools MCP.
If Chrome DevTools MCP is unavailable, stop and tell the user browser verification cannot run until it is installed.
Check the rendered page, not just the source.
If anything is broken, fix the source. Do not explain away visual defects.
Reload and verify again. Repeat until the browser output is clean.