verify-ui
Skill0 starsChanged 11 days agoMITView on GitHub
Check a UI change in a real browser before calling it done. Starts or finds the dev server, opens the changed pages, takes screenshots at phone and desktop widths in light and dark mode, reads console errors, and looks for layout bugs that typecheck and curl miss. Use after any change to pages, components, or styles, or when the user says "check it visually", "screenshot it", "does it look right", or "verify the UI".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- jonmumm/skillstheir own version, first seen Oct 21, 2026
- oliver-kriska/prmarmottheir own version, first seen Oct 7, 2026
- ThisIsSadeghi/KMPilottheir own version, first seen Aug 4, 2026
- ThisIsSadeghi/Loupetheir own version, first seen Jul 5, 2026
Used with
Projects with it also use cut-release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.
Also in 3 projects that use this
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ThisIsSadeghi/KMPilot★ 56same name
- oliver-kriska/prmarmot★ 9same name
- jonmumm/skills★ 2same name
- rpraharaj/ai-engineer★ 1same name
- ThisIsSadeghi/Loupe★ 1same name
- rpraharaj/ai-sdlc★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use what the session has: Playwright, a browser automation tool, or a headless browser script.
- Distinctive: line 23
Read every screenshot. Do not only save it.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.jsonscripts, 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.
3. Check
- Text that overflows, is clipped, or overlaps.
- Horizontal scroll on the phone width.
- Text that is hard to read on its background (most common in dark mode).
- Images that are missing, stretched, or very slow.
- Console errors and failed network requests (read the console log).
- The change itself: is the new thing there and does it do what was asked?
4. Fix and repeat
Fix what you found, take new screenshots, and compare. Stop after three rounds and report what remains.
5. Report
Pages checked, widths and modes, the problems found and fixed, and anything still open. Attach or link the final screenshots. Delete temporary screenshots that are not useful to keep, and never commit them unless asked.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.