Agent skill · software engineering · borghei
playwright-pro
End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
Why this skill is useful
Adds executable scripts for generating tests, diagnosing flaky tests, and migrating from Cypress/Selenium that are not commonly found in public documentation.
What it needs
Requires playwright installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Playwright Pro Production-grade end-to-end testing with Playwright. Generate tests from user stories, implement the Page Object pattern for maintainability, apply the correct locator strategy for resilient tests, diagnose and fix flaky tests, migrate from Cypress or Selenium, integrate with CI/CD, run visual regression tests, and perform accessibility audits. Enforces the 10 golden rules that eliminate 90% of E2E test failures. Core Capabilities Resilient authoring — getByRole/getByLabel/getByText locator priority, web-first auto-retrying assertions, and the 10 golden rules. Page Object Model — centralize locators, expose user-intent methods, generate POM classes from HTML/selectors. Test generation — produce specs from user stories with happy-path and error-path coverage. Flaky-test diagnosis — trace analysis, headed/debug runs, race-condition and shared-state fixes. Migration — Cypress/Selenium → Playwright command mapping and auth-setup patterns. CI integration — GitHub Actions, sharding, conditional browser installs, trace/screenshot artifacts. Visual regression & accessibility — toHaveScreenshot baselines and Axe WCAG AA gates. When to Use Writing or organizing E2E tests for web apps. Fixing flaky tests or diagnosing CI-only failures. Migrating a suite from Cypress or Selenium. Adding visual regression or WCAG accessibility gates. Setting up Playwright CI integration and reporting. Clarify First Before generating tests, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Task / sub-skill — init, generate, fix-flaky, migrate, or review (routes the entire workflow) [ ] User story or flow to cover — the happy + error paths the spec must assert (drives test generation) [ ] Locator surface — whether the app exposes roles/labels/data-testid (sets locator strategy and POM resilience) [ ] Source framework (if migrating) — Cypress or Selenium (selects the command-mapping table) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/playwright-pro