playwright

Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test selectors, flaky tests, authentication state, API mocking, hydration testing, parallel execution, CI configuration, or debugging test failures.

1,149
installs: 0 up / 0 down, score 0.00
votes: 218
repo stars
Updated: 2 months ago
In the catalog since: 6 Oct 2026
From: pproenca/dot-skills

Get it through your agent npx skills add pproenca/dot-skills@playwright

Skill instructions

Rendered from the published SKILL.md, 113 lines.

Playwright + Next.js Testing Best Practices

Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests.

When to Apply

Reference these guidelines when:

Writing new Playwright tests for Next.js apps
Debugging flaky or failing tests
Optimizing test execution speed
Setting up authentication state reuse
Configuring CI/CD pipelines for testing
Testing Server Components and App Router features
Reviewing test code for reliability issues

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Test Architecture	CRITICAL	`arch-`
2	Selectors & Locators	CRITICAL	`loc-`
3	Waiting & Assertions	HIGH	`wait-`
4	Authentication & State	HIGH	`auth-`
5	Mocking & Network	MEDIUM-HIGH	`mock-`
6	Next.js Integration	MEDIUM	`next-`
7	Performance & Speed	MEDIUM	`perf-`
8	Debugging & CI	LOW-MEDIUM	`debug-`

Quick Reference

1. Test Architecture (CRITICAL)

arch-test-isolation - Use fresh browser context for each test
arch-parallel-execution - Enable parallel test execution
arch-page-object-model - Use Page Object Model for complex pages
arch-fixtures - Use fixtures for shared setup
arch-test-production - Test against production builds
arch-cleanup-state - Clean up test state after each test

2. Selectors & Locators (CRITICAL)

loc-role-selectors - Use role-based selectors over CSS
loc-data-testid - Use data-testid for dynamic elements
loc-label-selectors - Use getByLabel for form inputs
loc-text-selectors - Use getByText for static content
loc-avoid-xpath - Avoid XPath selectors
loc-chained-locators - Chain locators for specificity
loc-placeholder-selector - Use getByPlaceholder sparingly

3. Waiting & Assertions (HIGH)

wait-web-first-assertions - Use web-first assertions
wait-avoid-hard-waits - Avoid hard waits
wait-network-idle - Use network idle for complex pages
wait-action-retries - Let actions auto-wait before interacting
wait-soft-assertions - Use soft assertions for non-critical checks
wait-custom-timeout - Configure timeouts appropriately

4. Authentication & State (HIGH)

auth-storage-state - Reuse authentication with storage state
auth-multiple-roles - Use separate storage states for different roles
auth-session-storage - Handle session storage for auth
auth-api-login - Use API login for faster auth setup
auth-parallel-workers - Use worker-scoped auth for parallel tests

5. Mocking & Network (MEDIUM-HIGH)

mock-api-responses - Mock API responses for deterministic tests
mock-intercept-modify - Intercept and modify real responses
mock-har-files - Use HAR files for complex mock scenarios
mock-abort-requests - Abort unnecessary requests
mock-network-conditions - Simulate network conditions

6. Next.js Integration (MEDIUM)

next-wait-hydration - Wait for hydration before interacting
next-server-components - Test server components correctly
next-app-router-navigation - Test App Router navigation patterns
next-server-actions - Test server actions end-to-end
next-baseurl-config - Configure baseURL for clean navigation

7. Performance & Speed (MEDIUM)

perf-sharding - Use sharding for large test suites
perf-headless-ci - Use headless mode in CI
perf-browser-selection - Select browsers strategically
perf-reuse-server - Reuse development server when possible
perf-retries - Configure retries for flaky test recovery

8. Debugging & CI (LOW-MEDIUM)

debug-trace-viewer - Use trace viewer for failed tests
debug-screenshots-videos - Capture screenshots and videos on failure
debug-inspector - Use Playwright Inspector for interactive debugging
debug-ci-reporters - Configure reporters for CI integration

How to Use

Read individual reference files for detailed explanations and code examples:

Section definitions - Category structure and impact levels
Rule template - Template for adding new rules

Reference Files

File	Description
AGENTS.md	Complete compiled guide with all rules
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "playwright"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository pproenca/dot-skills
Listing on skills.sh

From pproenca/dot-skills via skills.sh

Related skills

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 (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
97,885 installs
playwright-skill
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
6,248 installs
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.
5,246 installs
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD
3,310 installs
playwright-e2e-testing
Playwright modern end-to-end testing framework with cross-browser automation, auto-wait, and built-in test runner
2,706 installs

More from pproenca/dot-skills

zod
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
7,003 installs
vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
5,970 installs
react-hook-form
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, the subscribe() API, and the Watch / FormStateSubscribe / FieldArray render-prop components. Covers RHF 7.82 additions including resetDefaultValues() and the disabled field-array option. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).
2,979 installs
emilkowal-animations
Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.
2,794 installs
nuqs
nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.
2,322 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.