Skip to content

dvy1987/agent-loom / .agents/skills/browser-testing-with-devtools

browser-testing-with-devtools

Verified

Test and debug browser UIs using Chrome DevTools MCP — DOM inspection, console errors, network requests, performance traces, and visual verification. Load when building or debugging anything that renders in a browser, verifying a UI fix, profiling Core Web Vitals in a real page, or the user asks for browser testing with DevTools. Requires chrome-devtools MCP configured. Not for backend-only or CLI work. Pairs with frontend-design and performance-optimization.

Browser Testing with DevTools

Use Chrome DevTools MCP to verify runtime behavior — what the user sees, not what static analysis guesses.

Hard Rules

  • Verify in browser before claiming a UI fix works.
  • Use isolated profile by default (--isolated); never use personal browser for untrusted pages.
  • Read-only JS in page context unless user explicitly approves mutations.
  • Capture evidence: screenshot, console excerpt, network failure, or trace — not vibes.
  • Reproduce from a clean navigation when debugging flaky UI.

Setup (chrome-devtools MCP)

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest", "--isolated"]
    }
  }
}

Use --autoConnect only when logged-in state is required — document the security trade-off.


Workflow

Step 1 — Define what to verify

State: URL, user action, expected DOM/console/network outcome.

Step 2 — Navigate and observe

  • Screenshot for visual state
  • Console for errors/warnings
  • Network for failed requests or wrong payloads
  • DOM/a11y tree for structure and labels

Step 3 — Diagnose

Map symptom → tool: layout → computed styles; slow paint → performance trace; API bug → network panel.

Step 4 — Fix in code, re-verify

Same steps as Step 2 after change; keep before/after screenshots when useful.

Step 5 — Report

Include evidence snippets and whether issue is fully resolved or partially mitigated.


When NOT to use

  • Pure server/API changes with no browser surface
  • Environments where MCP cannot run (document manual repro instead)

Gotchas

  • Stale service worker caches mask fixes — hard refresh or disable SW when debugging.
  • Flaky tests from animation timing — wait for stable selectors.
  • --autoConnect exposes personal cookies and history.
  • Executing arbitrary JS in page can mutate production-like data.

Common Rationalizations

ExcuseReality
"The code looks correct"Runtime DOM, CSS cascade, and race conditions disagree.
"Unit tests cover it"JSDOM does not run full layout, fonts, or real network.
"I'll check the browser later"Later never comes; verify before marking done.
"MCP is too heavy"One screenshot + console read often saves hours of guesswork.
"It's just a CSS tweak"Tweaks cause CLS and overflow bugs visible only live.

Output Format

## Browser verification — [feature]

URL: [path]
Steps: [actions]
Evidence: [screenshot/console/network]
Result: [pass/fail + notes]

Examples


Verification

  • Reproduced issue in browser with evidence captured
  • Post-fix verification on same steps
  • No new console errors on happy path
  • Isolated profile used (or autoConnect risk documented)
  • Network/DOM findings tied to specific code change

Red Flags

  • UI fix claimed done without browser verification
  • Personal browser profile used on untrusted pages
  • Page-context JS mutates state without explicit approval
  • Stale service worker cache masks whether fix works

Prune Log

Last pruned: 2026-07-04

  • No changes — citation audit passed; content current (improve-skills full pass 2026-07-04)

Impact Report

URL: [path] | Issue: [one line]
Evidence: [screenshot/console/network]
Status: [fixed/partial/blocked]
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall