playwright-interactive

Debug web and Electron applications with persistent Playwright sessions via js_repl.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/luiztrilha/dunderia-public --skill playwright-interactive-luiztrilha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-interactive
Source: https://github.com/luiztrilha/dunderia-public/tree/main/templates/local-runtime-profile/skills/codex/playwright-interactive
Command: npx skills add https://github.com/luiztrilha/dunderia-public --skill playwright-interactive-luiztrilha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, js_repl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides persistent browser and Electron debugging through js_repl, enabling fast iterative UI debugging without restarting the toolchain.

Core Features & Use Cases

  • Persistent js_repl Session: Maintain the same Playwright handles across iterations for continuous debugging.
  • Functional & Visual QA: Perform functional and visual quality assurance on web and Electron apps.
  • Use Case: Debug a web application by running a series of QA checks, including visual inspections and functional tests, without the need to restart the debugging environment.

Quick Start

Start a new Codex session with js_repl enabled and use the playwright-interactive skill to debug your web or Electron application.

Frequently Asked Questions about playwright-interactive

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

FAQPage Schema
How do I debug a web application with Playwright without restarting the environment?

You can debug web applications without restarting by using a persistent js_repl session. This maintains Playwright handles across iterations for continuous, fast UI debugging and functional QA checks.

Can I use Playwright for Electron application debugging?

Yes, Playwright supports Electron application debugging alongside web apps. It uses js_repl to maintain persistent browser handles, allowing iterative functional and visual QA without environment restarts.

What is persistent UI debugging and how does it work with js_repl?

Persistent UI debugging retains Playwright handles across iterations via js_repl. It prevents the toolchain from restarting, enabling continuous visual inspections and functional tests during web and Electron development.

Do I need js_repl enabled to run interactive Playwright QA checks?

Yes, js_repl must be enabled in your Codex session. Playwright interactive requires both the playwright and js_repl dependencies to maintain persistent handles for iterative functional and visual QA.

What's the best way to run iterative visual QA on a browser application?

The best way is using a persistent js_repl session with Playwright. It maintains browser handles across iterations, allowing you to run successive visual QA checks without restarting the debugging environment.

Why does my Playwright debugging session lose state between test iterations?

Sessions lose state when handles are not persisted. Using js_repl with Playwright maintains the same handles across iterations, preventing state loss and avoiding toolchain restarts during continuous UI debugging.