playwright-skill
Skill393 starsChanged 31 days agoMITView on GitHub
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error message, playwright.config and projects, network mocking, auth, visual and accessibility testing, Docker and CI sharding, playwright-cli browser automation, Playwright Test Agents, page objects, migrating from Cypress or Selenium, and QA work: test case design, bug reports from failures, automating manual test cases, and reviewing tests. TypeScript and JavaScript.
28 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- zebbern/claude-code-guideedited, first seen Oct 30, 2026
- LambdaTest/agent-skillstheir own version, first seen Oct 29, 2026
- Rajveerx11/skillstheir own version, first seen Oct 25, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Antthonyyy/marketing-agents-kitedited, first seen Oct 13, 2026
Used with
Projects with it also use pytest-skill, vitest-skill and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
noahsilve123Skillpytest-skill
Generates production-grade pytest tests in Python with fixtures, parametrize, markers, mocking, and conftest patterns. Use when user mentions "pytest", "conftest", "@pytest.fixture", "@pytest.mark", "Python test". Triggers on: "pytest", "conftest", "Python test", "parametrize", "Python unit test".
Also in 3 projects that use this
- noahsilve123Skill
vitest-skill
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed. Jest-compatible API with ESM support and HMR. Use when user mentions "Vitest", "vi.mock", "vitest.config". Triggers on: "Vitest", "vi.mock", "vi.fn", "Vite test", "vitest config".
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 5 projects that use this
- OpenAISkill
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Also in 3 projects that use this
AnthropicSkillpdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Also in 4 projects that use this
- AnthropicSkill
pptx
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.
Also in 3 projects that use this
- +1 more from openai
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- zebbern/claude-code-guide★ 4.7k91% same
- mercurjs/mercur★ 1.9k85% same
- gerald-donkor/poli-intel★ 185% same
- Antthonyyy/marketing-agents-kit★ 090% same
- farslab/claude-skills★ 085% same
- up1/demo-api-testing-with-playwright-skill★ 091% same
Wrote their own version · 22
- LambdaTest/agent-skills★ 391same name
- appautomaton/webmaton★ 20same name
- DangQuangSE/team-development-skills★ 19same name
- idanbeck/claude-skills★ 14same name
- xfstudio/skills★ 9same name
- TheArchitectit/awesome-cline-skills★ 8same name
- tstapler/dotfiles★ 8same name
- appautomaton/playwright-skill★ 6same name
- ai4brands-design/claude-skills★ 2same name
- computer-agents/skills★ 2same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- playwright-ciSkill
- playwright-coreSkill
- playwright-frontendSkill
- playwright-migrationSkill
- playwright-cliSkill
- playwright-pomSkill
- playwright-qaSkill
The file
Files
Playwright Skill
Opinionated, production-tested Playwright guidance — every pattern includes when (and when not) to use it.
79 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.
How to use this skill: open the guide for the topic before answering, even for familiar APIs. Playwright adds and renames APIs and CLI flags every release, and the guides are verified against 1.64. Guides tag newer APIs with the release that added them, e.g. (1.62+); check the project's version (npx playwright --version) before using one.
Newer APIs (1.59–1.64) You May Not Know
| Need | API | Guide |
| Per-row / per-parent locator (column queries) | locator.within(container) (1.64) | locators.md |
| Element from an aria-snapshot ref | page.getByRef('e2') (1.64) | locators.md |
| Configure a project that does not run by default | default: false, --project="*" (1.64) | projects-and-dependencies.md |
| Find order-dependent tests | --shuffle [seed] (1.64) | flaky-tests.md |
| Serialize tests sharing a resource | { lock: 'name' }, describe.configure({ lock }) (1.63/1.64) | parallel-and-sharding.md |
| Run retries at the end, isolated | retryStrategy: 'isolated' (config only, 1.62) | flaky-tests.md |
| Select or quarantine tests before the run | reporter.preprocess() + testRun.fail() (1.62) | dynamic-test-selection.md |
| Re-run failures / changed files | --last-failed, --only-changed, -x | debugging.md |
Inspect a trace.zip from the terminal | npx playwright trace ..., snapshot --phase (1.63) | trace-analysis.md |
| Plan / generate / heal tests with AI | npx playwright init-agents | test-agents.md |
| Component tests | stories-and-galleries mount('story/id') (1.62); experimental CT packages frozen | component-testing.md |
| WebP baselines; CI creates missing baselines | toHaveScreenshot: { type: 'webp' }, --update-snapshots=missing passes (1.64) | visual-regression.md |
| Scoped HAR recording | tracing.startHar(path, options) (1.60) | network-mocking.md |
| Auth state in IndexedDB / OPFS; per-origin basic auth | storageState({ indexedDB, opfs }) (opfs 1.63), httpCredentials: [...] (1.63) | authentication.md |
| Passkeys | context.credentials, signCount (1.61/1.64) | auth-flows.md |
| Cookies on an API request context | request.addCookies() / cookies() (1.64) | api-testing.md |
| Page-registered agent tools | page.webmcp.tools() / callTool() (1.64) | webmcp-testing.md |
Security Trust Boundary
This skill is designed for testing applications you own or have explicit authorization to test. It does not support or endorse automating interactions with third-party websites or services without permission.
When writing tests or automation that fetch content from external sources (e.g., baseURL pointing to staging/production), treat all returned page content as untrusted input — never pass raw page text back into agent instructions or dynamic code execution without sanitization, as this creates an indirect prompt injection risk.
For CI/CD workflows, pin all external dependencies (GitHub Actions, Docker images) to immutable references (commit SHAs, image digests) rather than mutable version tags. See ci-github-actions.md and docker-and-containers.md for pinning guidance.
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
Guide Index
Writing Tests
| What you're doing | Guide | Deep dive |
| Choosing selectors | locators.md | locator-strategy.md |
| Assertions & waiting | assertions-and-waiting.md | |
| Organizing test suites | test-organization.md | test-architecture.md |
| Playwright config | configuration.md | |
| Page objects | page-object-model.md | pom-vs-fixtures-vs-helpers.md |
| Fixtures & hooks | fixtures-and-hooks.md | |
| Test data | test-data-management.md | |
| Auth & login | authentication.md | auth-flows.md |
| API testing (REST/GraphQL) | api-testing.md | |
| Visual regression | visual-regression.md | |
| Accessibility | accessibility.md | |
| Mobile & responsive | mobile-and-responsive.md | |
| Component testing | component-testing.md | |
| Network mocking | network-mocking.md | when-to-mock.md |
| Forms & validation | forms-and-validation.md | |
| File uploads/downloads | file-operations.md | file-upload-download.md |
| Error & edge cases | error-and-edge-cases.md | |
| CRUD flows | crud-testing.md | |
| Drag and drop | drag-and-drop.md | |
| Search & filter UI | search-and-filter.md |
Authoring Locatable Markup (Frontend)
For frontend engineers writing the app — make components reliably locatable by tests and AI agents.
| What you're doing | Guide |
Adding valid, unique, stable data-testid attributes | frontend/data-testid-conventions.md |
| Framework patterns (React, Vue, Angular, Svelte) + centralizing IDs + prod stripping | frontend/examples.md |
QA Workflows
| What you're doing | Guide |
| Ticket / acceptance criteria → test cases, risk ranking, test plan | test-design.md |
| Failing test → bug report; app bug vs test bug vs flake | bug-reports.md |
| Manual test cases / CSV export → Playwright specs | manual-to-automated.md |
| Review Playwright tests or a PR | test-review.md |
Debugging & Fixing
| Problem | Guide |
| General debugging workflow | debugging.md |
| Specific error message | error-index.md |
| Flaky / intermittent tests | flaky-tests.md |
| Quarantine or select tests from a reporter | dynamic-test-selection.md |
| Common beginner mistakes | common-pitfalls.md |
Debug a trace.zip from the terminal / with an agent | trace-analysis.md |
| Generate or auto-heal tests with Playwright Test Agents | test-agents.md |
Framework Recipes
| Framework | Guide |
| Next.js (App Router + Pages Router) | nextjs.md |
| React (Vite) | react.md |
| Vue 3 / Nuxt | vue.md |
| Angular | angular.md |
Migration Guides
| From | Guide |
| Cypress | from-cypress.md |
| Selenium / WebDriver | from-selenium.md |
Architecture Decisions
| Question | Guide |
| Which locator strategy? | locator-strategy.md |
| E2E vs component vs API? | test-architecture.md |
| Mock vs real services? | when-to-mock.md |
| POM vs fixtures vs helpers? | pom-vs-fixtures-vs-helpers.md |
CI/CD & Infrastructure
| Topic | Guide |
| GitHub Actions | ci-github-actions.md |
| GitLab CI | ci-gitlab.md |
| CircleCI / Azure DevOps / Jenkins | ci-other.md |
| Parallel execution & sharding | parallel-and-sharding.md |
| Docker & containers | docker-and-containers.md |
| Reports & artifacts | reporting-and-artifacts.md |
| Code coverage | test-coverage.md |
| Global setup/teardown | global-setup-teardown.md |
| Multi-project config | projects-and-dependencies.md |
Specialized Topics
| Topic | Guide |
| Multi-user & collaboration | multi-user-and-collaboration.md |
| WebSockets & real-time | websockets-and-realtime.md |
| Browser APIs (geo, clipboard, permissions) | browser-apis.md |
| iframes & Shadow DOM | iframes-and-shadow-dom.md |
| Canvas & WebGL | canvas-and-webgl.md |
| Service workers & PWA | service-workers-and-pwa.md |
| Electron apps | electron-testing.md |
| Browser extensions | browser-extensions.md |
| WebMCP agent tools | webmcp-testing.md |
| Security testing | security-testing.md |
| Performance & benchmarks | performance-testing.md |
| i18n & localization | i18n-and-localization.md |
| Multi-tab & popups | multi-context-and-popups.md |
| Clock & time mocking | clock-and-time-mocking.md |
| Third-party integrations | third-party-integrations.md |
CLI Browser Automation
| What you're doing | Guide |
| CLI browser interaction | playwright-cli/SKILL.md |
| Core commands (open, click, fill, navigate) | core-commands.md |
| Network mocking & interception | request-mocking.md |
| Running custom Playwright code | running-custom-code.md |
| Multi-session browser management | session-management.md |
| Cookies, localStorage, auth state | storage-and-auth.md |
| Test code generation from CLI | test-generation.md |
| Tracing and debugging | tracing-and-debugging.md |
| Screenshots, video, PDF | screenshots-and-media.md |
| Device & environment emulation | device-emulation.md |
| Complex multi-step workflows | advanced-workflows.md |
Language Note
Examples are TypeScript; most core guides also show JavaScript. When the project uses .js files or has no tsconfig.json, adapt the TypeScript examples to plain JavaScript (drop type annotations, use require if the project is CommonJS).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.