VS Code native browser tool behavior for canvas-based games (Phaser 3, etc.).
Clean up browser artifacts, kill zombie processes, and free disk space after using Browser Subagent.
Test across multiple browsers and devices for cross-browser compatibility.
Full browser control for authenticated web interactions using Playwright scripts
Capture browser console, network, and performance logs for debugging.
Inspect and debug live web pages using the Chrome DevTools Protocol via the `bdg` CLI.
Browser debugging and automation using Playwright.
Integrating Chrome DevTools and browser automation via MCP for live UI inspection, screenshot-to-code workflows, and visual debugging.
Expert in building browser extensions that solve real problems -
Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.
Use when automating browser tasks - clicking, filling forms, taking screenshots, debugging UI, or testing web flows.
RLVR-inspired Loop Detection & Breaking.
Pre-flight resource check before launching Browser Subagent.
Browser-based QA and autonomous verification — Playwright, Chrome DevTools MCP, Computer Use for visual testing, pixel verification…
Discover project routes/URLs BEFORE planning browser navigation.
This skill should be used when users need to capture screenshots of web pages.
Browser automation using local browser profile
GUI-R1 inspired Self-Reflection protocol.
Manage and use a persistent local browser session for interactive runtime inspection and manual QA flows.
Creates site-specific browser-automation skills that drive real websites via Playwright MCP: discovery interview, persistent logged-in…
Use when choosing, implementing, or reviewing browser storage such as localStorage, sessionStorage, IndexedDB, cookies, client…