What problem does it solve? Manually verifying that a deployed feature actually works across pages, viewports, and user journeys is slow and error-prone. This Skill automates post-deployment QA by driving a real browser to catch console errors, broken links, layout regressions, and accessibility violations before users do. ## Core Features & Use Cases - Four-phase QA workflow: Runs smoke tests (console errors, network failures, Core Web Vitals), interaction tests (nav links, forms, auth flows), visual regression at three breakpoints, and WCAG 2.2 AA accessibility audits. - Safety-first execution: Defaults to read-only journeys, requires explicit opt-in plus a staging URL for mutating flows like checkout, and mandates test credentials with PII redaction. - Structured verdict report: Produces a Markdown QA report ending in a SHIP, SHIP WITH FIXES, DO NOT SHIP, or INCONCLUSIVE verdict. - Use Case: After deploying a PR to a preview URL, run the full QA suite to confirm the contact form shows error states, the hero section does not overflow at 375px, and no new axe-core violations were introduced. ## Quick Start Run a browser QA pass on my staging deployment at the preview URL and give me a ship verdict report.
