Version normalization (scope: only plugins/skills older than 2.7.0): - Bumped 52 plugin.json + 21 SKILL.md `version` fields from pre-2.7.0 values (1.0.0 / 2.0.x / 2.2.x / 2.3.x / 2.4.x / 2.5.x) to 2.9.0. Left 2.7.0+ packages untouched. Tool mirrors (.codex/.gemini/.vibe/ .hermes) excluded. All manifests still pass check_plugin_json --all. Doc count refresh (recomputed raw figures: 338 skills, 16 domains, 62 plugins, 533 Python tools, 676 references): - marketplace.json: both descriptions + metadata.version -> 2.9.0. - Root README: headline, badges (Skills 338, Agents 51+, Commands 87+), intro counts, convert section (338 skills / 9 tools), and the full domain table rebuilt to 16 domains summing to 338 (adds research-ops, business-operations, commercial, compliance-os; corrects product 17, marketing 46, c-level 66, ra-qm 18, finance 4, engineering 51/78). - Fixed stale per-skill README `Version:` lines left inconsistent by the bump (andreessen, c-level-agents, product-team, senior-qa). - Fixed stale domain README footers (product-team 17/17, c-level 66/66, project-management 9/9). - CLAUDE.md scope line, structure tree, highlight, and footer synced to the raw figures. https://claude.ai/code/session_01PUNmQVE4WYvcrzpq2anC3D |
||
|---|---|---|
| .. | ||
| .claude-plugin | ||
| agents | ||
| hooks | ||
| integrations | ||
| skills | ||
| .mcp.json | ||
| CLAUDE.md | ||
| LICENSE | ||
| README.md | ||
| settings.json | ||
Playwright Pro
Production-grade Playwright testing toolkit for AI coding agents.
Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack — all from your AI agent.
Install
# Claude Code plugin
claude plugin install pw@claude-skills
# Or load directly
claude --plugin-dir ./engineering-team/playwright-pro
Commands
| Command | What it does |
|---|---|
/pw:init |
Set up Playwright in your project — detects framework, generates config, CI, first test |
/pw:generate <spec> |
Generate tests from a user story, URL, or component name |
/pw:review |
Review existing tests for anti-patterns and coverage gaps |
/pw:fix <test> |
Diagnose and fix a failing or flaky test |
/pw:migrate |
Migrate from Cypress or Selenium to Playwright |
/pw:coverage |
Analyze what's tested vs. what's missing |
/pw:testrail |
Sync with TestRail — read cases, push results, create runs |
/pw:browserstack |
Run tests on BrowserStack, pull cross-browser reports |
/pw:report |
Generate a test report in your preferred format |
Quick Start
# In Claude Code:
/pw:init # Set up Playwright
/pw:generate "user can log in" # Generate your first test
# Tests are auto-validated by hooks — no extra steps
What's Inside
9 Skills
Slash commands that turn natural language into production-ready Playwright tests. Each skill leverages Claude Code's built-in capabilities (/batch for parallel work, Explore for codebase analysis, /debug for trace inspection).
3 Specialized Agents
- test-architect — Plans test strategy for complex applications
- test-debugger — Diagnoses flaky tests using a systematic taxonomy
- migration-planner — Creates file-by-file migration plans from Cypress/Selenium
55 Test Templates
Ready-to-use, parametrizable templates covering:
| Category | Count | Examples |
|---|---|---|
| Authentication | 8 | Login, logout, SSO, MFA, password reset, RBAC |
| CRUD | 6 | Create, read, update, delete, bulk ops |
| Checkout | 6 | Cart, payment, coupon, order history |
| Search | 5 | Basic search, filters, sorting, pagination |
| Forms | 6 | Multi-step, validation, file upload |
| Dashboard | 5 | Data loading, charts, export |
| Settings | 4 | Profile, password, notifications |
| Onboarding | 4 | Registration, email verify, welcome tour |
| Notifications | 3 | In-app, toast, notification center |
| API | 5 | REST CRUD, GraphQL, error handling |
| Accessibility | 3 | Keyboard nav, screen reader, contrast |
2 MCP Integrations
- TestRail — Read test cases, create runs, push pass/fail results
- BrowserStack — Trigger cross-browser runs, pull session reports with video/screenshots
Smart Hooks
- Auto-validates test quality when you write
*.spec.tsfiles - Auto-detects Playwright projects on session start
- Zero configuration required
Integrations Setup
TestRail (Optional)
Set environment variables:
export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="your@email.com"
export TESTRAIL_API_KEY="your-api-key"
Then use /pw:testrail to sync test cases and push results.
BrowserStack (Optional)
export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"
Then use /pw:browserstack to run tests across browsers.
Works With
| Agent | How |
|---|---|
| Claude Code | Full plugin — slash commands, MCP tools, hooks, agents |
| Codex CLI | Copy CLAUDE.md to your project root as AGENTS.md |
| OpenClaw | Use as a skill with SKILL.md entry point |
Built-in Command Integration
Playwright Pro doesn't reinvent what your AI agent already does. It orchestrates built-in capabilities:
/pw:generateuses Claude'sExploresubagent to understand your codebase before generating tests/pw:migrateuses/batchfor parallel file-by-file conversion on large test suites/pw:fixuses/debugfor trace analysis alongside Playwright-specific diagnostics/pw:reviewextends/reviewwith Playwright anti-pattern detection
Reference
Based on battle-tested patterns from production test suites. Includes curated guidance on:
- Locator strategies and priority hierarchy
- Assertion patterns and auto-retry behavior
- Fixture architecture and composition
- Common pitfalls (top 20, ranked by frequency)
- Flaky test diagnosis taxonomy
License
MIT