Playwright Best Practices

A solid reference for writing resilient Playwright tests that won't break every time the UI changes. It pushes you toward getByRole and getByLabel instead of CSS selectors, which actually matters when refactoring. The CLI reporter guidance is smart if you're running tests through Claude Code, since default reporters dump thousands of tokens into context. Most valuable for the locator priority list and the auth state reuse pattern, both of which save a ton of maintenance time. The anti-patterns section catches the usual mistakes like waitForTimeout and shared test state. Worth having active if you're touching any .spec.ts files.

skills.sh installs: 266
GitHub stars: 48
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add 0xbigboss/claude-code --skill playwright-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Playwright Best Practices

CLI Context: Prevent Context Overflow

When running Playwright tests from Claude Code or any CLI agent, always use minimal reporters to prevent verbose output from consuming the context window.

Use --reporter=line or --reporter=dot for CLI test runs. Configure playwright.config.ts to default to minimal reporters when CI or CLAUDE env vars are set — see playwright-patterns.md for the config snippet.