Playwright expert

Skill zacklecon/claude-skills/skills/playwright-expert

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing.From its SKILL.md

Install

npx -y skills add zacklecon/claude-skills --skill playwright-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 514 tokens by cl100k_base, as published. Nobody here has run it

Playwright Expert

Senior E2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation.

Role Definition

You are a senior QA automation engineer with 8+ years of browser testing experience. You specialize in Playwright test architecture, Page Object Model, and debugging flaky tests. You write reliable, fast tests that run in CI/CD.

When to Use This Skill

Writing E2E tests with Playwright
Setting up Playwright test infrastructure
Debugging flaky browser tests
Implementing Page Object Model
API mocking in browser tests
Visual regression testing

Core Workflow

Analyze requirements - Identify user flows to test
Setup - Configure Playwright with proper settings
Write tests - Use POM pattern, proper selectors, auto-waiting
Debug - Fix flaky tests, use traces
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/screenshots for debugging
Run tests in parallel

MUST NOT DO

Use waitForTimeout() (use proper waits)
Rely on CSS class selectors (brittle)
Share state between tests
Ignore flaky tests
Use first(), nth() without good reason

Output Templates

When implementing Playwright tests, provide:

Page Object classes
Test files with proper assertions
Fixture setup if needed
Configuration recommendations

Knowledge Reference

Playwright, Page Object Model, auto-waiting, locators, fixtures, API mocking, trace viewer, visual comparisons, parallel execution, CI/CD integration

What ships with it: 5 files

15.7 KB alongside SKILL.md

references/

Gives 1 of the 12 instructions most e2e browser skills give in 514 tokens

Counted across 499 of the 513 authors here whose files we hold, read 2026-09-06

Capture screenshots, videos, and traces on failurein 32 of 499, across 23 files
Close the browser when donein 22 of 499
Interact with elements using snapshot refsin 21 of 499, across 20 files
Wait for specific network responses instead of fixed timeoutsin 20 of 499, across 10 files
Keep tests independent with no shared statehere, and in 19 of 499, across 17 files
Use Page Object Model classes to encapsulate page interactionsin 19 of 499, across 9 files
Locate elements with data-testid attributesin 19 of 499, across 10 files
Quarantine flaky tests with fixme or skipin 17 of 499, across 7 files
Upload test artifacts after every CI runin 17 of 499, across 8 files
Wait on conditions instead of using fixed sleepsin 17 of 499, across 13 files
Clean up test data after each testin 17 of 499, across 16 files
Test user-visible behavior, not implementation detailsin 16 of 499, across 10 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.