playwright
Pack path:
playwright/
Skills
Section titled “Skills”- Playwright Auth Projects And Isolation — Use when reusing authenticated state or modeling multiple user roles in Playwright without leaking state between tests. Covers storage state, setup projects, browser contexts, role-based projects, and the rule that isolation should stay intact even when login is optimized away.
- Playwright Debugging Traces And Flake Reduction — Use when a Playwright test is flaky, failing only in CI, or needs investigation rather than another retry. Covers traces, inspector, UI mode, codegen cleanup, and turning intermittent failures into concrete synchronization or contract fixes.
- Playwright Default Test Architecture — Choose a stable Playwright test architecture before writing more tests. Use when tasks mention Playwright adoption, test folder layout, fixture boundaries,
playwright.config.ts, projects, retries, parallelism, CI posture, browser coverage, or deciding which Playwright follow-up skill should own the work. - Playwright Locators Assertions And User Visible Contracts — Use when writing or fixing Playwright tests that should stay stable against UI refactors. Covers locators, actionability, web-first assertions, accessible roles, text and label contracts, and the rule that tests should bind to user-visible semantics before DOM structure.
- Playwright Network Control And API Synchronization — Use when Playwright tests need stable synchronization with backend behavior or deliberate network control. Covers request waiting, route interception, mocking boundaries, API request contexts, and the rule that tests should not over-mock what they actually need to verify.