verify-ui-change

Verifies UI changes end-to-end with Playwright screenshots, console checks, and guardrail tests.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill verify-ui-change-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-ui-change
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/verify-ui-change
Command: npx skills add https://github.com/sethdavis512/iridium --skill verify-ui-change-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI changes often get declared done after a successful compile, leaving broken layouts, console errors, and theme or viewport regressions undiscovered until review. This Skill enforces a repeatable verification workflow that produces visual evidence before any UI change is reported as complete. ## Core Features & Use Cases - End-to-end verification workflow: Boots the app on a dedicated port, interacts with the change via a throwaway Playwright spec, and asserts real state changes rather than mere visibility. - Screenshot evidence matrix: Captures before/after shots across light and dark themes and desktop and phone viewports, with animations disabled and time elements masked for stable images. - Guardrail test integration: Runs the relevant e2e spec, visual inventory tests, and responsive tests, and fails verification on any new console error or warning. - Use Case: After editing a React component that changes a settings page layout, use this Skill to boot the app, click through the new layout, capture light/dark and desktop/phone screenshots, confirm zero console errors, and attach the evidence to the PR. ## Quick Start Verify the UI change I just made to the settings page by booting the app, interacting with it in Playwright, and capturing before and after screenshots in light and dark mode.

Frequently Asked Questions about verify-ui-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a UI change with Playwright before merging?

Boot the app on a dedicated port, write a throwaway Playwright spec that interacts with the change and asserts the expected state, then capture screenshots across themes and viewports. Finish by running the guardrail e2e and visual tests and attaching the screenshots as evidence.

How to test UI in both light and dark mode with Playwright?

Use a theme-switching helper like setTheme to explicitly set light and dark modes rather than leaving the system default. Capture a screenshot in each theme at both desktop (1280x720) and phone (390x844) viewports for a minimum four-shot matrix.

Should I capture before screenshots when changing existing UI?

Yes, capture the current state first by stashing the change or checking out the base ref, screenshotting, then restoring. Skip before shots only for brand-new surfaces where no prior state exists.

Why does sign-in hang during Playwright e2e tests?

Sign-in silently hangs when the BETTER_AUTH_BASE_URL and VITE_BETTER_AUTH_BASE_URL environment variables do not match the port the app is booted on. Set both URLs to the same dedicated port, such as http://localhost:7780.

When should I not run end-to-end UI verification?

Skip this workflow for server-only changes such as models, API routes, and env plumbing, as well as documentation updates and pure test edits. It is designed only for changes that alter rendered markup, styling, or theming.