playwright-interactive

To maintain a persistent Playwright session for iterative web debugging, use this skill to preserve browser handles and state across runs without restarting the toolchain. It enables rapid debugging and regression checks by keeping the session active.

Yes, you can debug Electron apps using a persistent Playwright session provided by this skill. It supports cross-context session reuse across both desktop and web targets, allowing you to manage multiple contexts during visual QA.

Yes, you need Node.js and browser binaries installed to run Playwright interactive QA. The skill requires a configured Playwright setup in your workspace with js_repl support to initialize and manage the persistent debugging session.

The best way to reuse browser contexts during Playwright regression checks is to apply a persistent session approach. This skill maintains stable handles and state across iterations, preventing restart overhead and enabling cross-context validation.

Your Playwright toolchain restarts during rapid debugging iterations because standard runs do not preserve handles by default. This skill solves that problem by maintaining a persistent session, reducing restart overhead, and preserving state across runs.