From pw
Playwright testing toolkit — run existing tests or generate new ones from OpenSpec feature specs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pw:pwThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Coordinate Playwright test running and generation from a single entry point.
Coordinate Playwright test running and generation from a single entry point.
| Scenario | Command |
|---|---|
| Run existing Playwright tests (full suite or filtered) | /pw:run |
| Generate new Playwright tests from an OpenSpec feature spec | /pw:gen |
| Quick check — run tests then review failures | /pw:run → read report |
| Command | Purpose |
|---|---|
/pw:run [test-path or grep] [--headed] [--project=...] | Run Playwright tests, collect artifacts, summarize failures |
/pw:gen [path-to-openspec.md] [output-dir] | Convert an OpenSpec feature spec into Playwright test files |
OpenSpec (what to test) → pw:gen (generate tests) → pw:run (execute tests)
Generate once, run often. Tests land in tests/ui/generated/ by default.
npx claudepluginhub krayzpipes/claude-plugins --plugin pwGenerates Playwright tests from user stories, URLs, components, or features. Explores codebase, uses templates for auth, CRUD, checkout, and follows best practices for locators and assertions.
Guides Playwright end-to-end testing for web apps with cross-browser support (Chromium, Firefox, WebKit), visual regression, API testing, and mobile emulation. Use for E2E tests and UI automation workflows.
Sets up Playwright test projects with installation commands, basic/advanced playwright.config.ts configurations, multi-browser projects, and webServer for scalable test suites.