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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywrightExecute the skills CLI command in your project's root directory to begin installation:
Fetches playwright from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate playwright. Access via /playwright in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
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.
Reference these guidelines when:
| 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- |
arch-test-isolation - Use fresh browser context for each testarch-parallel-execution - Enable parallel test executionarch-page-object-model - Use Page Object Model for complex pagesarch-fixtures - Use fixtures for shared setuparch-test-production - Test against production buildsarch-cleanup-state - Clean up test state after each testloc-role-selectors - Use role-based selectors over CSSloc-data-testid - Use data-testid for dynamic elementsloc-label-selectors - Use getByLabel for form inputsloc-text-selectors - Use getByText for static contentloc-avoid-xpath - Avoid XPath selectorsloc-chained-locators - Chain locators for specificityloc-placeholder-selector - Use getByPlaceholder sparinglywait-web-first-assertions - Use web-first assertionswait-avoid-hard-waits - Avoid hard waitswait-network-idle - Use network idle for complex pageswait-action-retries - Let actions auto-wait before interactingwait-soft-assertions - Use soft assertions for non-critical checkswait-custom-timeout - Configure timeouts appropriatelyauth-storage-state - Reuse authentication with storage stateauth-multiple-roles - Use separate storage states for different rolesauth-session-storage - Handle session storage for authauth-api-login - Use API login for faster auth setupauth-parallel-workers - Use worker-scoped auth for parallel testsmock-api-responses - Mock API responses for deterministic testsmock-intercept-modify - Intercept and modify real responsesmock-har-files - Use HAR files for complex mock scenariosmock-abort-requests - Abort unnecessary requestsmock-network-conditions - Simulate network conditionsnext-wait-hydration - Wait for hydration before interactingnext-server-components - Test server components correctlynext-app-router-navigation - Test App Router navigation patternsnext-server-actions - Test server actions end-to-endnext-baseurl-config - Configure baseURL for clean navigationperf-sharding - Use sharding for large test suitesperf-headless-ci - Use headless mode in CIperf-browser-selection - Select browsers strategicallyperf-reuse-server - Reuse development server when possibleperf-retries - Configure retries for flaky test recoverydebug-trace-viewer - Use trace viewer for failed testsdebug-screenshots-videos - Capture screenshots and videos on failuredebug-inspector - Use Playwright Inspector for interactive debuggingdebug-ci-reporters - Configure reporters for CI integrationRead individual reference files for detailed explanations and code examples:
| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
Registry listing for playwright matched our evaluation — installs cleanly and behaves as described in the markdown.
playwright has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: playwright is focused, and the summary matches what you get after install.
We added playwright from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
playwright is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
playwright fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
playwright reduced setup friction for our internal harness; good balance of opinion and flexibility.
playwright fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
playwright is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend playwright for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 64