playwright-prolisted

# Playwright Pro Skill ## When to activate - Writing E2E tests for web applications with Playwright - Setting up the Page Object Model (POM) pattern for maintainable tests - Debugging flaky or intermittently failing tests - Setting up network interception to mock API responses in tests - Adding visual regression testing to your test suite - Integrating Playwright into CI/CD pipelines ## When NOT to use - Unit tests or component tests — use Vitest or Jest - API-only testing without UI — use supertest or httpx - Load testing — Playwright is for correctness, not performance - Simple smoke tests that change often — too much maintenance cost for shallow tests ## Instructions ### Project setup and configuration ``` Set up Playwright for [project]. Framework: [Next.js / React / Vue / Svelte / plain HTML] Test scope: [critical user journeys / full regression / smoke tests] Browsers: [Chromium / Firefox / WebKit / all three] CI: [GitHub Actions / GitLab CI / CircleCI] Setup: npm init playwright@latest # Choose: TypeScript, tests/ directory, GitHub Actions workflow playwright.config.ts: import { defineConfig, devices } from '@playwright/test'; export default defineConfig({ testDir: './tests', timeout: 30000, retries: process.env.CI ? 2 : 0, // Retry in CI only workers: process.env.CI ? 1 : undefined, // Serial in CI, parallel locally reporter: [ ['html'], // Local HTML report ['github'], // G