.github/skills/engineering-team/playwright-pro/SKILL.md
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.
npx skillsauth add desenyon/infinitecontex playwright-proInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Production-grade Playwright testing toolkit for AI coding agents.
When installed as a Claude Code plugin, these are available as /pw: commands:
| Command | What it does |
|---|---|
| /pw:init | Set up Playwright — detects framework, generates config, CI, first test |
| /pw:generate <spec> | Generate tests from user story, URL, or component |
| /pw:review | Review tests for anti-patterns and coverage gaps |
| /pw:fix <test> | Diagnose and fix failing or flaky tests |
| /pw:migrate | Migrate from Cypress or Selenium to Playwright |
| /pw:coverage | Analyze what's tested vs. what's missing |
| /pw:testrail | Sync with TestRail — read cases, push results |
| /pw:browserstack | Run on BrowserStack, pull cross-browser reports |
| /pw:report | Generate test report in your preferred format |
The recommended sequence for most projects:
1. /pw:init → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate → generates tests from your spec or URL
3. /pw:review → validates quality and flags anti-patterns ← always run after generate
4. /pw:fix <test> → diagnoses and repairs any failing/flaky tests ← run when CI turns red
Validation checkpoints:
/pw:generate — always run /pw:review before committing; it catches locator anti-patterns and missing assertions automatically./pw:fix — re-run the full suite locally (npx playwright test) to confirm the fix doesn't introduce regressions./pw:migrate — run /pw:coverage to confirm parity with the old suite before decommissioning Cypress/Selenium tests.# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"
# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.
# 2. Review the generated tests
/pw:review tests/auth/login.spec.ts
# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.
# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed
# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()
getByRole() over CSS/XPath — resilient to markup changespage.waitForTimeout() — use web-first assertionsexpect(locator) auto-retries; expect(await locator.textContent()) does notbaseURL in config — zero hardcoded URLs2 in CI, 0 locally'on-first-retry' — rich debugging without slowdowntest.extend() for shared state1. getByRole() — buttons, links, headings, form elements
2. getByLabel() — form fields with labels
3. getByText() — non-interactive text
4. getByPlaceholder() — inputs with placeholder
5. getByTestId() — when no semantic option exists
6. page.locator() — CSS/XPath as last resort
export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="[email protected]"
export TESTRAIL_API_KEY="your-api-key"
export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"
See reference/ directory for:
golden-rules.md — The 10 non-negotiable ruleslocators.md — Complete locator priority with cheat sheetassertions.md — Web-first assertions referencefixtures.md — Custom fixtures and storageState patternscommon-pitfalls.md — Top 10 mistakes and fixesflaky-tests.md — Diagnosis commands and quick fixesSee templates/README.md for the full template index.
testing
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
development
Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making. Use when analyzing financial statements, building valuation models, assessing budget variances, or constructing financial projections and forecasts. Also applicable when users mention financial modeling, cash flow analysis, company valuation, financial projections, or spreadsheet analysis.
testing
SaaS financial health advisor. Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing.
development
Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making. Use when analyzing financial statements, building valuation models, assessing budget variances, or constructing financial projections and forecasts. Also applicable when users mention financial modeling, cash flow analysis, company valuation, financial projections, or spreadsheet analysis.