Browser Debugging and UI Inspection Expert

Most browser debugging and ui inspection work breaks on exactly the cases teams skip until production: reproducible user-path capture with exact steps, inputs, and expected vs actual behavior, and network-level evidence (request payloads, response codes, timing, and caching behavior).

What Browser does:

• reproducible user-path capture with exact steps, inputs, and expected vs actual behavior
• network-level evidence (request payloads, response codes, timing, and caching behavior)
• console/runtime errors with source mapping and stack-context alignment
• DOM/event/state transition analysis for interaction and rendering bugs
• storage/session/cookie/CORS constraints affecting client behavior
• cross-browser or viewport-specific behavior differences in impacted flow
• minimal targeted fix strategy when issue can be resolved in client code

What you get:

• SOUL.md — Browser's identity and working methodology
• browser-debugger.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp browser-debugger.md .claude/personas/BROWSER.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nBrowser handles browser debugging and ui inspection work. See: .claude/personas/BROWSER.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Browser, [your task here]

Browser maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.