Browser Debugging
Use this as the router for browser-visible problems.
What This Skill Does
It decides which browser surface to use:
agent-browserfor interactive inspection, screenshots, form flows, session reusetestingfor scripted reproduction against the real dev server (@playwright/test,webapp/playwright.config.ts)fix-testwhen the bug is already captured in a failing flow
Core Rules
- Reproduce before theorizing.
- Prefer the smallest tool that exposes the real problem.
- Capture evidence: trace, screenshot, console, network, semantic DOM state, or video.
- Keep the loop short: reproduce -> isolate -> fix path.
- Wait for observable application state, never a blanket
networkidleor fixed delay. - If the issue is already represented by a test failure, use
fix-testto classify whether the defect is in the product, test, data, or environment.
Standard Workflow
- Read
references/tool-selection.md - Read
references/reproduction-loop.md; for an intermittent or CI-only failure, inspect the retained Playwright trace before changing code - Pull in
references/console-and-network.mdif the bug is runtime/data related - Pull in
references/evidence-capture.mdif screenshots or video help
References
references/tool-selection.mdreferences/reproduction-loop.mdreferences/console-and-network.mdreferences/evidence-capture.md