What problem does it solve? Setting up Playwright involves three separate steps (package install, browser download, system dependencies), and missing any one causes cryptic errors like "Executable doesn't exist" or tests that pass locally but fail in CI. This Skill guides verification, diagnosis, and repair of Playwright installations. ## Core Features & Use Cases - Installation Verification: Runs the three-step install checklist (package, browsers, system deps) and validates each stage with commands like npm ls @playwright/test and npx playwright install --dry-run. - Error Diagnosis: Maps common error messages (missing executables, missing Linux libraries, launch timeouts, race conditions) to concrete fixes, with a detailed error reference in resources/common-errors.md. - CI Configuration: Provides ready-to-adapt pipeline patterns for GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps, including browser caching and test sharding. - Use Case: A developer's tests pass locally but fail in GitHub Actions with "Executable doesn't exist". Invoke this Skill to identify the missing npx playwright install --with-deps step and get a corrected workflow file. ## Quick Start Ask the assistant to verify my Playwright installation and diagnose why browser tests fail in CI.