verify-ui

Installation
SKILL.md

Verify UI

Goal: you saw the change working before the user does. A clean typecheck does not prove a page looks right.

1. Get a running page

  • Find the dev command (package.json scripts, README). If a dev server already runs, use it. Do not start a second one on another port without telling the user.
  • Find the exact routes the change affects. Include one page that only uses a shared component you changed.
  • For a page behind login, ask the user for a test account or a way in. Do not bypass auth.

2. Look at it

Use what the session has: Playwright, a browser automation tool, or a headless browser script. For each route take screenshots at:

  • 390 px wide (phone) and 1280 px wide (desktop).
  • Light and dark mode, if the site has both.
  • One interaction state that matters (menu open, form error, empty list, loading).

Read every screenshot. Do not only save it.

Installs
2
First Seen
3 days ago