Pw
Production-grade Playwright testing toolkit.
Before & after
Same prompt, same agent — the only difference is the skill.
Playwright tests are a good way to catch regressions. You could write tests for important flows, set them up to run in CI, and adjust when things break. There are templates and examples out there. What flows are most important to test first?
PLAYWRIGHT TEST SUITE: CRITICAL FLOWS (3 test files): 1. SIGNUP → LOGIN → PAYMENT ✓ New user creation (email + password) ✓ Email verification click-through ✓ Login with valid credentials ✓ MFA code entry (if enabled) ✓ Billing page load + stripe integration ✓ Payment success and redirect 2. CONTENT CREATION → PUBLISH ✓ New post creation (title, description, image upload) ✓ Auto-save every 2 seconds ✓ Publish to live (date/time scheduling works) ✓ Post visible in feed after 30s 3. SOCIAL SHARE ✓ Copy social link to clipboard ✓ Open Twitter share intent (verify URL params) ✓ Email share opens mail client TEST FIXTURES (auto-setup): → Database: Insert test user + test post data → Auth: Issue valid session token (skip manual login) → Stripe: Mock payment endpoint (no real charges) CI/CD INTEGRATION: • Run on: Every PR + main branch commits • Parallelism: 4 workers (reduce 12m → 3m test time) • Fail strategy: Block merge if any test fails • Report: HTML dashboard showing pass/fail per flow FLAKY TEST HANDLING: → Screenshot on failure (debug visual state) → Retry once automatically (catch transient timing issues) → Alert if same test fails 2+ times in a row (underlying issue) TEMPLATES PROVIDED: • 55 pre-built test templates (form filling, navigation, API mocking) • 3 test agents (one for setup, one for data validation, one for performance) MAINTENANCE: Update tests when UI changes (selector drift is #1 pain point).
About this skill
name: pw description: Use when Production-grade Playwright testing toolkit.
Pw
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the pw skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Pw; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: pw
description: Use this skill when the user mentions Playwright tests, end-to-end testing, flaky test fixes, test migration from another framework, or CI test suite configuration.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Pw
Applies a production-grade Playwright workflow: write reliable end-to-end tests, diagnose and fix flaky failures, migrate suites from other frameworks, and configure CI for speed and stability.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.