e2e-skills

Use this skill to find the root cause of a Cypress end-to-end test that has already run and failed, and fix it. Reach for it whenever someone shares a failing Cypress spec and wants to know why — a Timed-out-retrying command, a selector that never resolves, a cy.intercept alias that never matches or a request that races the assertion, a hook that skips the rest of the suite, a flake that only passes on retry, a hydration or timing race, or a passes-locally-but-fails-in-CI split. It applies given any failure evidence: a mochawesome or JUnit report, an error message or stack, screenshots or videos, or CI artifacts (a GitHub run id to download). Use it to determine whether the failure is a real product regression or a brittle test, and to propose the concrete fix. Do not use it for writing new Cypress tests, reviewing a passing suite, non-Cypress test failures (Playwright, Jest, Vitest), or debugging the app/backend with no Cypress test involved.

Static review of Playwright/Cypress E2E specs and Page Objects (POM) — catch tests that pass CI but prove nothing. Triggers: review tests, audit test quality, find weak/flaky/silently-passing tests, missing awaits, anti-patterns, coverage gaps, tests pass but miss bugs. Not for runtime failure debugging (use playwright-debugger / cypress-debugger). Flags 24 anti-patterns grouped P0 (must-fix, silent always-pass), P1 (poor diagnostics), P2 (maintenance).

Use this skill to find the root cause of a Playwright end-to-end test that has already run and failed, and fix it. Reach for it whenever someone shares a failing Playwright spec or test and wants to know why — a TimeoutError, a broken or ambiguous selector, a whole spec breaking after a deploy, a flake that only passes on retry, a hydration or timing race, or a passes-locally-but-fails-in-CI split. It applies given any failure evidence: an error message, a playwright-report/ or HTML report, a trace.zip, screenshots, or CI artifacts (including a GitHub run id to download). Use it to determine whether the failure is a real product regression or a brittle test, and to propose the concrete fix. Do not use it for writing new Playwright tests, speeding up or reviewing a passing suite, non-Playwright test failures (Cypress, Jest, Vitest), or debugging the app or backend when no Playwright test is involved.

Use this skill to generate new Playwright end-to-end tests from scratch — for a page, a user flow, a form, or a component — taking them from zero to reviewed, passing specs. Reach for it whenever someone wants to add, write, create, or scaffold Playwright E2E coverage, fill coverage gaps for uncovered routes, or bootstrap the first e2e test for a project and set up its conventions. It explores the live page to discover real selectors, proposes a scenario plan for approval, generates Page Object or flat specs that match the existing project style, then runs an e2e review and the suite before handing back. Do not use it for debugging an existing failing Playwright test (use playwright-debugger), reviewing or auditing tests that already pass (use e2e-reviewer), generating Cypress tests, or writing unit, component, or integration tests with Jest, Vitest, or Testing Library.