What problem does it solve? Features often ship with unit and integration tests but no verification that the full user journey works from browser to database and back, leaving auth flows, permission boundaries, and rejection paths unverified at the system level. ## Core Features & Use Cases - Critical Journey Identification: Derives 5-10 critical user journeys from spec REQ-NNN acceptance criteria, prioritized by blast radius (auth, payments, CRUD, permissions), including rejection paths. - Playwright Setup & Patterns: Provides config, Page Object Model structure, semantic locator priority, auth fixtures with storageState, and anti-pattern rules (no hardcoded waits, no CSS selector coupling). - Accessibility Testing: Integrates axe-playwright for WCAG 2.1/2.2 AA checks on every critical page, with EU compliance support and a reusable checkAccessibility helper. - CI Integration: Adds an E2E job that runs against staging after deployment, with sharding, artifact uploads, and secrets management. - Use Case: After implementing a checkout feature, use this Skill to generate Playwright specs covering login, add-to-cart, payment success and decline paths, plus axe accessibility scans, then wire them into a post-deploy CI job. ## Quick Start Use the e2e-testing skill to write Playwright tests for the critical user journeys in my current feature spec and add accessibility checks.
