skills.rest
metric-space-ai
metric-space-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

playwright-interactive

Maintain a persistent Playwright session for iterative web and Electron QA.

2|Updated Apr 12, 2026
Search Tags:#playwright#electron#web-testing#persistent-session#interactive-debugging#js_repl#qa-evidence
One-click install
npx skills add https://github.com/metric-space-ai/ctox --skill playwright-interactive-metric-space-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-interactive
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/packs/testing/playwright-interactive
Command: npx skills add https://github.com/metric-space-ai/ctox --skill playwright-interactive-metric-space-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to debug local web or Electron apps by maintaining a persistent Playwright session across iterations, reducing setup and teardown overhead and preserving handles between runs.

Core Features & Use Cases

  • Persistent browser and Electron session across iterations to avoid reinitialization.
  • Reuse of top-level handles (browser, context, page, electronApp, appWindow) to speed up iterative QA.
  • Supports web and Electron debugging workflows with ongoing evidence capture and results verification.

Quick Start

Initialize a persistent Playwright session in your project directory and begin interactive debugging using the provided steps.

Frequently Asked Questions about playwright-interactive

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

FAQPage Schema
How do I keep a Playwright session persistent across multiple debugging iterations?▼

You can maintain a persistent Playwright session across iterations by reusing top-level handles like browser, context, and page objects. This avoids reinitialization overhead and preserves your application state between consecutive debugging runs.

Can I reuse Playwright browser handles when debugging an Electron app?▼

Yes, you can reuse top-level handles including electronApp and appWindow across debugging iterations. This preserves your Electron session state and significantly speeds up repetitive UI testing workflows.

What is the best way to debug iterative UI changes without resetting the browser context?▼

The best way to debug iterative UI changes is maintaining a persistent web or Electron session. By preserving context and page handles in a JS REPL sandbox, you avoid setup and teardown overhead between each modification.

Does interactive debugging in a JS REPL sandbox support ongoing QA evidence capture?▼

Yes, interactive debugging in a JS REPL sandbox supports ongoing evidence capture. It allows you to cross-check renders and verify results continuously while maintaining a persistent Playwright session for local apps.

Why does my Playwright test reinitialize the browser every time I run a new check?▼

Your Playwright test reinitializes the browser because the session is not persisted across iterations. You need a persistent session management approach to reuse top-level handles and avoid repeated setup and teardown overhead.

Related Skills

Explore More Software Engineering Skills→
jackspacejackspace
16

Browser Daemon

Maintain a persistent Playwright-driven Chrome session via file-based IPC commands.

Community
Advanced
DEEP-PolyUDEEP-PolyU

playwright-interactive

Automate persistent Playwright debugging sessions for local web and Electron apps.

Official
Advanced
open-wattopen-watt
2

test-openwatt

Automate unit and runtime testing for the OpenWatt application.

Official
Advanced
Moisesjr20Moisesjr20
1

vercel-sandbox

Run agent-browser inside ephemeral Vercel Sandbox microVMs for isolated browser automation.

Community
Advanced