playwright-interactive

Maintain persistent Playwright handles and contexts for iterative UI debugging.

3|Updated Jan 14, 2022

Search Tags:#debugging #qa #playwright #electron #web #persistent-session #js_repl

Ready to run

npx skills add https://github.com/bingran-you/bingran-you --skill playwright-interactive-bingran-you

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwright-interactive
Source: https://github.com/bingran-you/bingran-you/tree/main/repo-skills/playwright-interactive
Command: npx skills add https://github.com/bingran-you/bingran-you --skill playwright-interactive-bingran-you

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a stable, long-lived Playwright session for debugging local web and Electron applications, enabling handles and contexts to be reused across iterations to reduce startup time and flaky restarts.

Core Features & Use Cases

Persistent web and Electron QA sessions with shared handles (browser, context, page, and Electron app window) across iterations.
Guided bootstrap, mode switching between explicit viewport and native window, and session reuse during iterative development.
End-to-end QA and visual verification for local apps, including debugging workflows that require running a local server and launching an Electron workspace.

Quick Start

Start a persistent Playwright session in your workspace and begin iterative UI debugging.

Frequently Asked Questions about playwright-interactive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain a persistent Playwright session for iterative UI debugging?▼

You can maintain a persistent Playwright session by enabling the js_repl feature to keep browser, context, and page handles alive across code edits, reducing startup time and flaky restarts during iterative UI debugging.

Can I use Playwright to debug local Electron apps without restarting the toolchain?▼

Yes, you can debug local Electron apps without restarting the toolchain by launching a persistent workspace session that preserves the Electron app window handle across multiple QA iterations and rapid visual verification checks.

How do I switch between explicit viewport and native window modes in Playwright QA?▼

You can switch between explicit viewport and native window modes during a Playwright QA session by following the guided bootstrap steps, allowing flexible visual verification for both local web and Electron applications.

Do I need to enable js_repl to reuse browser contexts across Playwright edits?▼

Yes, you must enable the js_repl feature to reuse browser contexts and handles across edits, which is required to follow the setup and bootstrap steps for maintaining a stable, long-lived Playwright debugging environment.

Why does my Playwright debugging session flake or restart during local web app testing?▼

Playwright debugging sessions flake or restart because standard configurations drop handles after each execution, whereas using a persistent session with shared contexts prevents these disruptive restarts during local web app testing.

What is the best way to run rapid QA checks on local web apps using Playwright?▼

The best way to run rapid QA checks is to start a persistent Playwright session in your workspace, which allows you to reuse shared handles and contexts for iterative development without restarting the entire toolchain.