bondar-artem
- 11 skills
- 0 followers
- 9 hours ago last updated
- ▌ Pw Init · bondar-artemInitialize a Playwright E2E framework in a brand-new project. Installs Playwright, then scaffolds config, directory structure, multi-environment env files, auth setup, fixtures skeleton, sample smoke tests, npm scripts, and tooling.
- ▌ Pw New Test · bondar-artemWrite a new Playwright E2E test from user-provided test steps. Reviews existing tests, inspects source code, writes the test, then runs and debugs it if needed.
- ▌ Pw Debug Live · bondar-artemDebug a Playwright test interactively via `--debug=cli` and `playwright-cli`. Pauses the test at a user-chosen line using `pause-at` (no source edits), then drives the live, paused page with `snapshot`, `eval`, `generate-locator`, `console`, `requests` to diagnose race conditions, timing bugs, and state-dependent failures that a static trace can't show. Use when the user asks to "step through a test", "live debug", "attach to a paused test", "debug from line N", or when `pw-debug-test` (trace-based) was insufficient because the failure depends on live page state.
- ▌ Pw Debug Test · bondar-artemDebug a failed Playwright test by running it with tracing on, then analyzing the trace using the Playwright CLI trace tool (`npx playwright trace`). Use this skill whenever the user asks to debug, fix, or investigate a failing or flaky Playwright test, or when a test execution produces an error. Also triggers when the user says things like "this test is broken", "why is this test failing", "fix this test", or "investigate test failure".
- ▌ Pw Test Audit · bondar-artemAudit a recently written Playwright test as a fresh pair of eyes. Reviews only the most recent uncommitted changes via git diff, checks compliance with the project's Playwright scripting rules, architecture, and POM conventions, and reports findings before optionally applying fixes.
- ▌ Pw New Test CLI · bondar-artemWrite a new Playwright E2E test from user-provided test steps when application source code is NOT accessible. Uses Playwright CLI (`@playwright/cli`) to inspect a live URL via snapshots and `generate-locator`, then writes the test, runs and debugs it if needed.
- ▌ Pw Debug Actions · bondar-artemDebug a Playwright test that failed in GitHub Actions. Uses the `gh` CLI to locate the failed workflow run, downloads its `test-results` artifact (containing the Playwright trace), analyzes the trace via `npx playwright trace`, identifies the root cause, and applies a fix to the spec following the project's Playwright scripting rules — leaving the change uncommitted so the user can review, commit, and push. Use this skill when the user asks to debug, fix, or investigate a Playwright test that failed on GitHub Actions / CI (e.g. "the pw test failed on CI", "debug the failed actions run", "why did the GitHub Actions Playwright job fail", "fix the failing CI test").
- ▌ Pw Coverage Planner · bondar-artemPlan Playwright E2E test coverage for a parent scenario. Enters plan mode, researches existing tests and source code, brainstorms positive/edge/negative cases, and saves an approved coverage plan as a markdown artifact in `.claude/pw-plans/` for later test generation.
- ▌ Pw Refactor Into Pom · bondar-artemRefactor existing Playwright tests into a Page Object Model architecture with a PageManager class and a single `pom` fixture. Detects existing POM and mimics its style; bootstraps the POM infrastructure when none exists. Enforces project-specific POM conventions — locators inline in methods, no tiny methods, strict page boundaries, entry/exit validation, dedicated validation methods, and reuse-first method design.
- ▌ Init Playwright Scripting · bondar-artemAdd the Playwright scripting rule to a project's `.claude/rules/` folder. Installs E2E test authoring conventions — locators, assertions, waiting, test structure, naming, code style, actions, and form interactions. Use when adding Playwright to a new project or refreshing the scripting rule in an existing one.
- ▌ Init Playwright Architecture · bondar-artemAdd the Playwright architecture rule to a project's `.claude/rules/` folder. Installs Page Object conventions, custom fixtures, auth setup with storageState, directory structure, config best practices, and anti-patterns. Use when adding Playwright to a new project or refreshing the architecture rule in an existing one.