playwright-best-practices
Skill1 starsChanged 41 days agoNo licenceView on GitHub
Playwright best practices for E2E, component, API, visual, and accessibility testing: flaky-test fixes, Page Object Model, CI/CD, mocking, auth/OAuth, axe-core, uploads, WebSockets, mobile, GraphQL, PWA, Electron, and extensions. Use when writing or debugging Playwright tests. NOT for: non-Playwright frameworks (Cypress/Selenium-only) or general CI without Playwright.
20 other projects use a version of this, 13 of them edited.
Adopted by
Most recently taken up by
- figueroaignacio/ignaciofigueroa.devedited, first seen Nov 8, 2026
- ever-co/ever-worksedited, first seen Nov 8, 2026
- ever-works/ever-worksedited, first seen Nov 5, 2026
- lecluse-net/galaristheir own version, first seen Oct 30, 2026
- lcx9451/dsh-engineering-skill-packedited, first seen Oct 25, 2026
- ldaume/agentic-engineering-harnesstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use nodejs-backend-patterns, next-cache-components and 10 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.
xfstudioSkillnodejs-backend-patterns
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
Also in 5 projects that use this
VercelSkillnext-cache-components
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
Also in 4 projects that use this
GitHubSkillmulti-stage-dockerfile
Create optimized multi-stage Dockerfiles for any language or framework
Also in 3 projects that use this
VercelSkillnext-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods
Also in 3 projects that use this
midudevSkilltailwind-css-patterns
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.
Also in 3 projects that use this
KadajettSkillnestjs-best-practices
NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.
Also in 3 projects that use this
- +1 more from vercel-labs
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 13
- sanity-io/sanity★ 6.4k90% same
- currents-dev/playwright-best-practices-skill★ 42090% same
- tazo90/next-openapi-gen★ 19690% same
- ever-co/ever-works★ 19090% same
- ever-works/ever-works★ 19090% same
- figueroaignacio/ignaciofigueroa.dev★ 790% same
- lcx9451/dsh-engineering-skill-pack★ 390% same
- dennisgr7/snob-cli★ 290% same
- idexal/idexal-skills★ 290% same
- FabienDehopre/triple-yahtzee-score-board★ 190% same
3 more not listed
Wrote their own version · 7
- flpbalada/fb-skills★ 8same name
- ldaume/agentic-engineering-harness★ 3same name
- kimtth/agent-skill-100-lines-or-less★ 2same name
- lecluse-net/galaris★ 1same name
- hossainks/claude-skill★ 0same name
- jgamaraalv/delivery-loop★ 0same name
- simu5116/ClaudeCode★ 0same name
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 repository93 other files it gives its agents.
- accessibility-auditorSkill
- agent-dispatchSkill
- api-contract-validatorSkill
- architecture-patternsSkill
- audit-itemSkill
- autonomous-investigationSkill
- battle-card-builderSkill
- cicd-pipelineSkill
- codebase-designSkill
- code-reviewSkill
- company-intelSkill
- competitive-analysis-processSkill
- competitive-intel-watchSkill
- competitive-research-snapshotSkill
- config-scanSkill
- core-rulesSkill
- coverage-matrixSkill
- customer-journey-mapSkill
- ddd-aggregatesSkill
- ddd-context-mapSkill
- ddd-contextsSkill
- ddd-discoverSkill
- ddd-domain-interactionsSkill
- ddd-model-reviewSkill
- ddd-openspec-bridgeSkill
- ddd-qa-chainSkill
- ddd-scopeSkill
- ddd-subdomainsSkill
- ddd-tactical-reviewSkill
- decision-logSkill
- deep-codebase-analysisSkill
- delegated-researchSkill
- dependency-scanSkill
- discovery-interview-prepSkill
- electron-best-practicesSkill
- env-checkSkill
- event-stormingSkill
- executing-plansSkill
- experiment-handoffSkill
- frontend-designSkill
- git-workflowSkill
- grill-meSkill
- intelligence-collection-disciplinesSkill
- jobs-to-be-doneSkill
- k6-performanceSkill
- llm-gateway-opsSkill
- marketing-copywritingSkill
- market-landscape-scanSkill
- perf-checkSkill
- pipeline-0to1Skill
- pixel-perfectSkill
- plan-grillingSkill
- positioning-statementSkill
- positioning-workshopSkill
- prd-developmentSkill
- prd-driven-dddSkill
- press-releaseSkill
- problem-handlingSkill
- problem-statementSkill
- product-doc-auditSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 3 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

