What problem does it solve? End-to-end test suites often hardcode one framework, grow to cover every click path, and rot with flaky tests that either block CI forever or get silently deleted. This Skill maps only the critical user journeys, auto-detects whichever E2E driver is actually available at runtime, and quarantines flaky tests with tracked review dates instead of ignoring them. ## Core Features & Use Cases - Runtime driver detection: Checks for Claude's browser tools, Chrome DevTools MCP, the project's own Playwright setup, or native desktop automation — never assumes a specific tool is installed. - Journey mapping and Page Object Model: Prioritizes flows by risk (auth, payment, irreversible actions first) and writes tests against intention-revealing page objects so UI changes touch one file. - Flake quarantine and failure artifacts: Confirms flakiness with repeated runs, quarantines with tracking notes and review dates, and captures screenshots, video, and traces on failure only. - Alternate modes: Post-deploy QA sweeps ending in a SHIP / DO NOT SHIP verdict, and demo walkthrough video recording with cursor overlay and pacing rules. - Use Case: After dev-kickoff flags a checkout flow as visual/layout work, hand it here to map the journey, author a Playwright test with page objects, run it, and capture failure artifacts as verification evidence. ## Quick Start Write an end-to-end test for the checkout flow using whatever browser driver is available in this project.
