What problem does it solve? Green test runs can hide broken UI: in a repository whose test environment is Node with no DOM, no test renders a component, so a change can break the browser render while every test passes. This Skill enforces browser-based verification of any user-visible change before it is reported as done. ## Core Features & Use Cases - Browser-driven verification: Open the affected page with browser automation (Claude in Chrome, Playwright, or a screenshot tool), perform the action, and inspect the result. - State and variant coverage: Check empty, loading, error, and long-content states, plus both locales, both themes, mobile width, and a second tenant for tenant-scoped apps. - Email template preview: Verify templates under emails/ via the react-email preview (pnpm dev:email) instead of sending real messages. - Honest reporting: Report the page, action, and observed result, or explicitly mark the change as unverified when the app could not be run. - Use Case: After editing a settings page layout, load /settings at mobile width in the browser, confirm the header renders correctly in both locales, and attach a screenshot to the final report. ## Quick Start Ask the assistant to verify the recent UI change in the browser by opening the affected page, exercising the empty and error states, and reporting what it actually saw.
