playwright-cli-setup

Name: playwright-cli-setup
Availability: InStock
Author: migletto

Drive a persistent Playwright CLI session for interactive Vela browser testing.

Updated Jul 21, 2026

Search Tags:#testing #debugging #browser automation #playwright #screenshot #vela

Ready to run

npx skills add https://github.com/migletto/slides --skill playwright-cli-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwright-cli-setup
Source: https://github.com/migletto/slides/tree/main/.claude/skills/playwright-cli-setup
Command: npx skills add https://github.com/migletto/slides --skill playwright-cli-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/cli.

What problem does it solve?

This Skill sets up and controls a persistent Playwright CLI browser session for exploring, testing, and debugging Vela without writing throwaway scripts.

Core Features & Use Cases

Interactive browser driving: Open a live render, inspect DOM state, click elements, press keys, and evaluate JavaScript step by step.
UX verification and debugging: Reproduce bugs, capture screenshots, validate slide navigation, and inspect presenter or gallery flows.
Container-aware setup: Handles offline file renders, pinned Chromium configuration, blocked CDNs, and per-agent session isolation for parallel testing.

Quick Start

Use the playwright-cli-setup skill to open a Vela offline render in a persistent browser session and inspect the current slide state interactively.

Frequently Asked Questions about playwright-cli-setup

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

FAQPage Schema

How do I debug Vela slides interactively without writing throwaway scripts?▼

You can debug Vela slides interactively without throwaway scripts by using a persistent Playwright CLI browser session to open a live render, inspect DOM state, click elements, and evaluate JavaScript step by step.

Can I use Playwright to capture screenshots and probe selectors in offline file renders?▼

Yes, Playwright can capture screenshots and probe selectors in offline file renders by driving a persistent browser session configured for offline file:// rendering and pinned Chromium control.

How does persistent browser session testing compare to running standard automated browser scripts?▼

Persistent browser session testing provides interactive, step-by-step browser driving for ad hoc exploration and debugging, whereas standard automated scripts execute linearly without interactive inspection or session continuity.

Does the interactive Vela browser testing setup support parallel agents and blocked CDNs?▼

Yes, the setup supports parallel testing through per-agent session isolation and handles container-aware configurations including blocked CDNs, offline file rendering, and pinned Chromium environments.

What is the best way to verify presenter and gallery flows in Vela?▼

The best way to verify presenter and gallery flows is by driving a persistent Playwright CLI session to navigate slides, inspect DOM state, and validate interactive user flows directly in a live browser.

Why does my Playwright browser session fail to render offline Vela files?▼

Offline Vela file rendering fails if the browser session lacks proper container-aware setup, requiring offline file:// rendering configuration and pinned Chromium settings to function correctly.