playwriter

Run Playwright scripts against a persistent Chrome session for UI testing.

3.1k|286|Updated Sep 7, 2025

Search Tags:#Playwright #QA #browser-automation #UI-testing #playwriter #persistent-session #web-dashboard

Ready to run

npx skills add https://github.com/mikeyobrien/ralph-orchestrator --skill playwriter-mikeyobrien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwriter
Source: https://github.com/mikeyobrien/ralph-orchestrator/tree/main/.claude/skills/playwriter
Command: npx skills add https://github.com/mikeyobrien/ralph-orchestrator --skill playwriter-mikeyobrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables browser automation by running Playwright scripts against a persistent Chrome session, preserving logins, cookies, and extensions to streamline UI testing and validation of web dashboards.

Core Features & Use Cases

Persistent browser sessions to avoid repeated logins and setup.
Execute Playwright code against a real Chrome session using a simple CLI workflow.
Ideal for validating Ralph web dashboard UI, automated QA tests, and accessibility snapshots.

Quick Start

Install the CLI: npm i -g playwriter Start a session: playwriter session new Run Playwright code against the session: playwriter -s <session_id> -e "await page.goto('https://example.com')" List sessions: playwriter session list

Frequently Asked Questions about playwriter

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

FAQPage Schema

How do I run Playwright tests against a persistent Chrome session?▼

To run Playwright tests against a persistent Chrome session, install the Playwriter CLI via npm, start a new session, and execute Playwright code using the session ID. This preserves logins and cookies for UI testing.

Does browser automation with Playwright support testing authenticated flows?▼

Yes, browser automation with Playwright supports testing authenticated flows by driving scripts against a persistent Chrome session. This approach preserves logins, cookies, and extensions to streamline validating web dashboards.

What do I need to start automating UI testing with Playwright?▼

To start automating UI testing with Playwright, you need the Playwriter CLI installed globally via npm, the Chrome extension, and a running Chrome instance with the extension enabled to execute scripts.

Can I capture accessibility snapshots across pages with Playwright?▼

Yes, you can capture accessibility snapshots across pages with Playwright by executing scripts against a persistent Chrome session. This allows you to validate UI compliance and test dashboard pages effectively.

Why use a persistent Chrome session instead of standard Playwright browser automation?▼

A persistent Chrome session avoids repeated logins and setup overhead during browser automation. It preserves your existing cookies and extensions, making it ideal for validating authenticated web dashboard flows.