ui-verification
Skill4 starsChanged 7 months agoMITView on GitHub
Use when a UI design, redesign, or handoff needs a final review for visual quality, state coverage, accessibility, and platform fit before it is treated as complete.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Tsuchiya2/evaluator-driven-agent-flowtheir own version, first seen Oct 15, 2026
- mblode/agent-skillstheir own version, first seen Sep 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- mblode/agent-skills★ 189same name
- Tsuchiya2/evaluator-driven-agent-flow★ 1same 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 repository6 other files it gives its agents.
- beautiful-uiSkill
- cinematic-web-experienceSkill
- framework-shadcn-tailwind-uiSkill
- platform-android-uiSkill
- platform-ios-uiSkill
- platform-web-uiSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 10
Use this skill at the end of UI design work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
UI Verification
Overview
Use this skill at the end of UI design work. Check that the output is visually coherent, covers important states, respects accessibility, and fits the intended platform.
Checklist Areas
- Visual direction consistency
- Design-system coherence
- Screen and component hierarchy
- Accessibility and readability
- State coverage
- Platform fit
- Implementation handoff completeness
- UI quality rubric score when comparing before/after examples or public proof artifacts
Pass Criteria
- The visual direction is specific enough to guide implementation.
- The system covers colors, typography, spacing, surfaces, states, and motion.
- Important screens include empty, loading, error, success, disabled, focus, and selection states where relevant.
- Accessibility notes include contrast, text scaling, focus behavior, and reduced motion.
- Platform guidance is native to the target, not generic web-first UI.
- Public examples meet the UI quality rubric threshold and avoid critical failures.
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.