verify-ui
Skill0 starsChanged 17 days agoMITView on GitHub
Exercise a UI change the way a user would — the changed flow, shared routes that read the same state, empty/error/loading, and desktop plus narrow viewports. Use when the change touches UI, when ready-to-merge dispatches it, or the user asks to verify the UI. Do not stop at a screenshot.
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- whyashthakker/estacktheir own version, first seen Nov 8, 2026
- rpraharaj/ai-engineeredited, 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
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-engineer★ 115% same
Wrote their own version · 5
- ThisIsSadeghi/KMPilot★ 56same name
- oliver-kriska/prmarmot★ 9same name
- jonmumm/skills★ 2same name
- ThisIsSadeghi/Loupe★ 1same name
- whyashthakker/estack★ 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.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
Files
Verify UI
Prove the changed UI still works for a person. A screenshot of the happy path is not enough.
Is this the right skill?
| Signal | Do this instead |
| Keyboard/name/contrast on the diff only | a11y-pass |
| Spec states of a screen | write-ui-spec |
| No UI in the diff | report n/a and stop |
Required inputs
- The UI diff
AGENTS.mdRun / e2e command if any
Human decisions (do not invent)
- Inventing a browser harness (do not)
Procedure
- Inventory routes, screens, components, CSS, and client state the change touches.
- Drive with the first that exists: browser/preview tool; this repo’s UI/e2e runner; running app + script; existing component test. If you cannot drive it, unverified and list what a human should click.
- Exercise: changed flow end to end; shared surfaces; empty/error/loading/denied; desktop and ~375px if layout changed; bar UI (name, keyboard, readable).
- Write references/verify-ui-template.md.
Output
- Path: reply
- Template:
references/verify-ui-template.md
Quality bar
- Not only a screenshot
- Shared surfaces considered or n/a
- Unverified if you only read code
Done
The template. Fixes: implement-change then re-run this skill.
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.