playwright-best-practices
Playwright Best Practices
Use When
- Writing new Playwright tests
- Reviewing Playwright test changes
- Fixing flaky Playwright tests
- Choosing locators, assertions, fixtures, projects, or debug settings
- Refactoring Playwright tests toward user-visible behavior
Do Not Use When
- Testing non-browser unit logic better covered by unit tests
- Writing tests for third-party sites or services you do not control
- Adding sleeps, retries, or larger timeouts to hide nondeterministic behavior
- Building Page Object Models before duplication or intent problems exist
Workflow
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
10discuss-task
Clarify ambiguous tasks before action. Use when goal, scope, success criteria, constraints, or risks are unclear.
7react-useeffect-avoid
Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.
6discuss-code
Critically discuss code issues with compact findings. Use when code needs review for logic, simplicity, structure, naming, or maintainability.
6react-key-prop
Guides proper usage of the key prop in React lists. Use this skill when rendering lists, mapping arrays to components, or troubleshooting list-related state bugs.
5cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion.
5