playwright-expert
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.
npx skills add Jeffallan/claude-skills --skill playwright-expert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Playwright Expert E2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation. ## Core Workflow 1. **Analyze requirements** - Identify user flows to test 2. **Setup** - Configure Playwright with proper settings 3. **Write tests** - Use POM pattern, proper selectors, auto-waiting 4. **Debug** - Run test → check trace → identify issue → fix → verify fix 5. **Integrate** - Add to CI/CD pipeline ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Selectors | `references/selectors-locators.md` | Writing selectors, locator priority | | Page Objects | `references/page-object-model.md` | POM patterns, fixtures | | API Mocking | `references/api-mocking.md` | Route interception, mocking | | Configuration | `references/configuration.md` | playwright.config.ts setup | | Debugging | `references/debugging-flaky.md` | Flaky tests, trace viewer | ## Constraints ### MUST DO - Use role-based selectors when possible - Leverage auto-waiting (don't add arbitrary timeouts) - Keep tests independent (no shared state) - Use Page Object Model for maintainability - Enable traces/screenshot
- Core Workflow
- Reference Guide
- Constraints
- MUST DO
- MUST NOT DO
- Code Examples
- Selector: Role-based (correct) vs CSS class (brittle)
- Page Object Model + Test File
- Debugging Workflow for Flaky Tests
- Output Templates
- Knowledge Reference
What does the playwright-expert skill do?
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.
How do I install it?
Run `npx skills add Jeffallan/claude-skills --skill playwright-expert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.