playwright-interactive

Maintain persistent Playwright sessions for iterative UI debugging and QA.

779|80|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Haohao-end/openagent --skill playwright-interactive-haohao-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-interactive
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/playwright-interactive
Command: npx skills add https://github.com/Haohao-end/openagent --skill playwright-interactive-haohao-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the slow, repetitive cycle of restarting browser automation every time you need to debug or visually verify a UI, by keeping a persistent Playwright session alive across iterations.

Core Features & Use Cases

  • Persistent js_repl + Playwright session: Reuse browser/context/page handles across runs to speed up iterative debugging.
  • Web and mobile QA modes: Validate UI behavior in a fixed viewport for reproducible screenshots, plus a dedicated mobile emulation path.
  • Electron QA support: Launch and reload Electron apps and capture renderer evidence without tearing down the whole workflow.
  • Functional + visual QA loop: Create a QA inventory, run functional checks with realistic input, then run a visual pass with viewport fit checks and screenshot-based evidence.
  • Session recovery guidance: Use restart/relaunch patterns when handles become stale, and treat js_repl reset as a destructive recovery tool.

Example use case: You’re shipping a new settings page and need to repeatedly test keyboard navigation, verify layout at multiple breakpoints, and capture evidence for signoff without losing the Playwright session state.

Quick Start

Use the playwright-interactive skill to start a persistent Playwright session, open your target local web or Electron app, then run the functional QA inventory and capture visual evidence.

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 alive across UI debugging iterations?

You can keep a persistent js_repl + Playwright session alive to reuse browser/context/page handles across runs, avoiding slow restarts during iterative UI debugging.

Can I use Playwright to test and capture screenshots of Electron desktop apps?

Playwright supports Electron QA by launching and reloading renderer processes to capture visual evidence without tearing down the entire automation workflow.

How do I run visual QA checks with viewport-fit screenshots for local web pages?

Use a fixed viewport for reproducible screenshots during functional and visual QA passes to validate layout behavior and capture evidence for signoff.

What is the best way to recover stale Playwright handles during an e2e testing loop?

Apply restart and relaunch patterns to recover stale handles, treating a js_repl reset as a destructive recovery tool when session state becomes invalid.

Does this Playwright workflow support mobile emulation for functional QA?

Yes, the workflow includes a dedicated mobile emulation path alongside web QA modes to validate UI behavior across different viewport constraints.