Playwright Skill
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and...
Install
npx skills add zebbern/claude-code-guide --skill playwright-skill -g -a claude-code -y- Repository
- zebbern/claude-code-guide4.7k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 2,916 tokens
- Runs scripts
- No, instructions only
What it does
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from Cypress/Selenium. TypeScript and JavaScript.
Playwright Skill
Opinionated, production-tested Playwright guidance, every pattern includes when (and when not) to use it.
50+ reference guides covering the full Playwright surface: selectors, assertions, fixtures, page objects, network mocking, auth, visual regression, accessibility, API testing, CI/CD, debugging, and more, with TypeScript and JavaScript examples throughout.
Golden Rules
getByRole()over CSS/XPath, resilient to markup changes, mirrors how users see the page- Never
page.waitForTimeout(), useexpect(locator).toBeVisible()orpage.waitForURL() - Web-first assertions,
expect(locator)auto-retries;expect(await locator.textContent())does not - Isolate every test, no shared state, no execution-order dependencies
baseURLin config, zero hardcoded URLs in tests- Retries:
2in CI,0locally, surface flakiness where it matters - Traces:
'on-first-retry', rich debugging artifacts without CI slowdown - Fixtures over globals, share state via
test.extend(), not module-level variables - One behavior per test, multiple related
expect()calls are fine - Mock external services only, never mock your own app; mock third-party APIs, payment gateways, email
