What problem does it solve? Verifying that a UI change actually works in a real browser is often skipped or done with unreliable open-ended visual judgment. This Skill runs a fixed, executable Playwright checklist against a running frontend app and cross-checks the actual git diff against the files claimed in tasks.md, producing paste-ready evidence for the verify phase. ## Core Features & Use Cases - Fixed checklist assertions: Generates and runs concrete Playwright tests (route loads, footer visible, form submits) selected from keyword-matched templates such as footer/nav visibility, form submission, list pagination, CRUD dialog, and dashboard/cards. - Scope verification: Compares the real git diff in the app directory against the ## Files section of tasks.md and fails on any file changed outside the claimed scope. - Structured evidence output: Prints a [x]/[ ] checklist with inline failure details plus a non-zero exit code on any failure, ready to paste verbatim into evidence.md. - Use Case: After implementing a legal footer in a Next.js app, run the harness against the local dev server to confirm the footer and its links render on the target route and that no files outside the declared change scope were modified. ## Quick Start Start the frontend dev server, then ask the agent to run the e2e QA harness with the app directory and the change's tasks.md to verify the UI change in a browser.
