playwright▌

Comprehensive reference guide for writing, debugging, and maintaining Playwright tests across all testing types and scenarios. \n \n Covers 50+ testing patterns including E2E, component, API, GraphQL, visual regression, accessibility, security, mobile, and Electron app testing \n Includes activity-based lookup tables for writing new tests, debugging failures, fixing flaky tests, and infrastructure setup \n Provides decision trees for test type selection, architecture patterns (POM vs fixtures),

Opinionated, production-tested Playwright guidance — every pattern includes when (and when not) to use it.

Drive a real browser from the terminal using playwright-cli. Prefer the bundled wrapper script so the CLI works even when it is not globally installed. Treat this skill as CLI-first automation. Do not pivot to @playwright/test unless the user explicitly asks for test files.

Playwright is a browser automation framework for Node.js and Python supporting Chromium, Firefox, and WebKit with a single API. It provides auto-waiting, web-first assertions, and full test isolation for reliable end-to-end testing.

When running Playwright tests from Claude Code or any CLI agent, always use minimal reporters to prevent verbose output from consuming the context window.

Use this skill when:

Hyvä replaces Luma's KnockoutJS/RequireJS/jQuery with Alpine.js + Tailwind CSS. Playwright's strict mode (rejects locators matching multiple elements) conflicts with Alpine.js DOM patterns where hidden elements exist throughout the page. This skill documents pitfalls and solutions discovered while writing Playwright tests for Hyvä storefronts.

symfony:e2e-panther-playwright

Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests.

Extract structured data from multiple web pages with respectful, ethical crawling practices.