What problem does it solve? Iterative UI debugging usually requires relaunching browsers and losing state between every code change. This Skill keeps a single Playwright session alive inside js_repl so you can reload pages, rerun functional and visual QA, and capture screenshots without restarting the toolchain. ## Core Features & Use Cases - Persistent Browser Sessions: Reuse the same Playwright handles (browser, context, page, Electron app) across iterations, reloading only what changed. - Web and Electron Support: Launch headed Chromium with explicit or native viewports, emulate mobile contexts, or launch Electron apps directly through Playwright. - Structured QA Workflow: Build a shared QA inventory, run functional checks with real user input, perform a separate visual QA pass, and verify viewport fit before signoff. - CSS-Normalized Screenshots: Emit model-ready screenshots with correct CSS pixel coordinates for both web pages and Electron windows. - Use Case: While fixing a layout bug in a local React app, keep the dev server and browser alive, reload after each edit, click through every control, and capture viewport screenshots proving the fix. ## Quick Start Use playwright-interactive to launch my local app at http://127.0.0.1:3000 in a persistent Playwright session and run functional and visual QA on it.
