browser-debugging
/browser-debugging
Investigate web UI failures, visual regressions, and browser performance. Use for browser testing, Playwright scripts, screenshots, console or network inspection, and cross-browser reproduction.
- Author
- hakula139 ↗
- Repository
- plugins ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Investigate web UI failures, visual regressions, and browser performance. Use for browser testing, Playwright scripts, screenshots, console or network inspection, and cross-browser reproduction.
Original author description
Investigate web UI failures, visual regressions, and browser performance. Use for browser testing, Playwright scripts, screenshots, console or network inspection, and cross-browser reproduction.
How it works
- Choose the tool
- Run standalone automation
- Gather evidence
SKILL.md preview
--- name: browser-debugging description: >- Investigate web UI failures, visual regressions, and browser performance. Use for browser testing, Playwright scripts, screenshots, console or network inspection, and cross-browser reproduction. compatibility: Requires Python Playwright for scripted runs --- # Browser Debugging ## Choose the tool Reuse available browser tools before installing Playwright or downloading browser binaries: - Use the assistant's native browser controls, when available, to navigate and inspect pages interactively. - Use Chrome DevTools MCP to capture performance traces and diagnose console errors and network issues. - Use Python Playwright to run reproducible scripts or compare Chromium, Firefox, and WebKit. ## Run standalone automation If `uv` is missing, enter a Nix shell: ```bash nix shell nixpkgs#uv ``` Run Python Playwright scripts in the Playwright environment that the global instructions or the project name, which pairs a Playwright version with its browser binaries. Without one, use a Python environment whose `playwright install` fetched the browsers for its own `playwright` package. Use headless mode by default, and choose Firefox or WebKit when the issue involves another engine: ```bash uv run --with playwright playwright install chromium firefox webkit uv run --with playwright python3 /tmp/browser-check.py ``` Run project-owned Playwright suites in their own environment, using the browser revisions required by their dependency version. A `PLAYWRIGHT_BROWSERS_PATH` holds the browsers of one Playwright version, so never point another version's driver at it. ## Gather evidence Reproduce the reported interaction at the relevant viewport and device scale. Wait for the content to render, then inspect the DOM and screenshots. Compare visuals under the same conditions, and inspect the images yourself. For performance issues, capture a trace while reproducing the interaction. Check scripting, layout, paint, and compositing costs, and inspect GPU status if acceleration may be involved. Record the browser engine, headless mode, and rendering backend alongside the measurements so differences from the user's desktop browser remain clear.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · hakula139/plugins | 100 | MIT |
| madappgang/magus | 100 | MIT |
Database snapshot: 13.11.2026 · package version 168ded39af8d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100browser-testing
Browser automation and testing using playwright-cli (stateful Bash CLI for scripted tests — network inspection, console monitoring, screenshots, tracing) and Browser-Use MCP (autonomous agent flows). Use when the user needs to test web apps, debug browser issues, analyze… - 100web-app-testing
Use when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find. Trigger on "check this works in the browser", "reproduce… - 100browser-recording
Records browser sessions via Playwright and converts video to GIF. Use when creating web UI tutorials or demos showing browser interactions. - 100webapp-testing
E2E strategy, Playwright scripts, and visual and accessibility checks. Use when testing a web app in a browser or auditing a deployed URL. - 100web-debug
You MUST use this when interacting with or testing local web applications with Playwright - verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs. - 85browser-diagnostics
Reproduce web UI failures using browser console, network, DOM, rendering, or performance evidence. Use when behaviour must be observed in a browser, not for ordinary static UI edits.