verify-ux-ui
Skill1 starsChanged 6 days agoMITView on GitHub
"Use after implementing or fixing UI, layout, styling, routing,
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- broSkill
- create-my-skillSkill
- glassmorphismSkill
- swiftui-designSkill
- humanizerSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- clean-up-git-historySkill
- commit-messageSkill
- commitSkill
- diagnoseSkill
- fixSkill
- grill-meSkill
- implementSkill
- loopSkill
- subagentsSkill
- update-docsSkill
- sudo-ssh-agent-authSkill
- unslopSkill
- visualize-skill-workflowSkill
- web-app-secSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 24
Check every screen, mode, or command that shares the state, data, or components you touched, and the surrounding flows, to catch …
- Distinctive: line 31
If verification finds a problem, fix it and re-verify.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify UX/UI
Principles
- A screenshot shows appearance, not behavior. Before declaring the task complete, confirm the change works in the app.
Workflow
- Exercise the changed feature end to end the way a real user would, and confirm behavior, not just appearance. Web: browser tools. Native and desktop (macOS, Windows, Linux): Computer Use or the platform's UI automation and screenshots. Mobile: simulator or emulator. CLI/TUI: run the command with real inputs and check output and exit codes. Games: play the changed path and check the on-screen result.
- Check every screen, mode, or command that shares the state, data, or components you touched, and the surrounding flows, to catch regressions.
- Cover the edge states your change touches: empty, error, and variants such as routes, flags, window sizes, devices, or inputs. If layout or styling changed, check the layouts a real user will see.
- If verification finds a problem, fix it and re-verify. If verification is impossible (no simulator, no access), say so in the report with the reason.
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.

