artifacts/bundle/skills/engineering-team/playwright-pro/SKILL.md
# Playwright Pro Production-grade Playwright testing toolkit for AI coding agents. ## Available Commands When installed as a Claude Code plugin, these are available as `/pw:` commands: | Command | What it does | | --------------------- | ----------------------------------------------------------------------- | | `/pw:init` | Set up Playwright — detects framework, generates config, CI, first test | | `/pw:gene
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/engineering-team/playwright-proInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Production-grade Playwright testing toolkit for AI coding agents.
When installed as a Claude Code plugin, these are available as /pw: commands:
| Command | What it does |
| --------------------- | ----------------------------------------------------------------------- |
| /pw:init | Set up Playwright — detects framework, generates config, CI, first test |
| /pw:generate <spec> | Generate tests from user story, URL, or component |
| /pw:review | Review tests for anti-patterns and coverage gaps |
| /pw:fix <test> | Diagnose and fix failing or flaky tests |
| /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 |
| /pw:browserstack | Run on BrowserStack, pull cross-browser reports |
| /pw:report | Generate test report in your preferred format |
The recommended sequence for most projects:
1. /pw:init → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate → generates tests from your spec or URL
3. /pw:review → validates quality and flags anti-patterns ← always run after generate
4. /pw:fix <test> → diagnoses and repairs any failing/flaky tests ← run when CI turns red
Validation checkpoints:
/pw:generate — always run /pw:review before committing; it catches locator anti-patterns and missing assertions automatically./pw:fix — re-run the full suite locally (npx playwright test) to confirm the fix doesn't introduce regressions./pw:migrate — run /pw:coverage to confirm parity with the old suite before decommissioning Cypress/Selenium tests.# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"
# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.
# 2. Review the generated tests
/pw:review tests/auth/login.spec.ts
# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.
# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed
# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()
getByRole() over CSS/XPath — resilient to markup changespage.waitForTimeout() — use web-first assertionsexpect(locator) auto-retries; expect(await locator.textContent()) does notbaseURL in config — zero hardcoded URLs2 in CI, 0 locally'on-first-retry' — rich debugging without slowdowntest.extend() for shared state1. getByRole() — buttons, links, headings, form elements
2. getByLabel() — form fields with labels
3. getByText() — non-interactive text
4. getByPlaceholder() — inputs with placeholder
5. getByTestId() — when no semantic option exists
6. page.locator() — CSS/XPath as last resort
export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="[email protected]"
export TESTRAIL_API_KEY="your-api-key"
export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"
See reference/ directory for:
golden-rules.md — The 10 non-negotiable ruleslocators.md — Complete locator priority with cheat sheetassertions.md — Web-first assertions referencefixtures.md — Custom fixtures and storageState patternscommon-pitfalls.md — Top 10 mistakes and fixesflaky-tests.md — Diagnosis commands and quick fixesSee templates/README.md for the full template index.
Creator: Engineering Team License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:engineering-teamOriginal Path:engineering-team/playwright-pro
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski