setup-playwrightlisted

# Setup Playwright Build the smallest reliable repo-owned Playwright setup that fits the repository's language, package boundaries, test runner, developer-tool, and CI conventions. This is a system skill: it leaves behind a repo-owned harness or an explicitly requested Playwright developer-tool artifact. Day-to-day test authoring and live browser investigation belong to `playwright-testing`. ## Ownership Boundary Use this skill when the main artifact is one or more of: - Playwright dependencies or browser binaries - runner config, package placement, or monorepo wiring - app startup through `webServer` or an ecosystem-native equivalent - browser, device, environment, retry, reporter, or artifact configuration - reusable-auth setup and ignored state files - a minimal smoke check that proves the harness works - CI install, smoke, sharding, or report-merge plumbing - an explicitly requested repo-owned `@playwright/cli` developer dependency or script - host-targeted Playwright Test Agent definitions for a compatible Node Playwright Test harness Use `playwright-testing` when the harness works and the task is a spec, test review, flake diagnosis, locator change, mock decision, visual check, or standalone `playwright-cli` investigation. If an environment-dependent install, startup, container, or CI failure has no established cause, start with `project-platform-diagnose` and return here once the repair is known. ## Choose The Existing Ecosystem Follow the strongest reposit