playwright-best-practices

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smok

Try your first task

Create a focused Playwright E2E test

Start a fresh conversation. Replace the highlighted placeholders.

Use the playwright-best-practices skill to draft one Playwright E2E test for [repository path] covering [small user scenario]. Follow the skill's guidance for test-suite structure, locators, assertions, and waiting. Explain any assumptions and do not modify files yet.

Required inputs

Repository path
Small user scenario to test

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

303 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗