ui-standards
Skill0 starsChanged 42 days agoMITView on GitHub
Review web, desktop, or mobile interfaces for consistency, interaction clarity, accessibility, and responsive behavior using the project's existing design system and requirements.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aubynsamuel/android-dev-skillstheir own version, first seen May 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aubynsamuel/android-dev-skills★ 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- jevSkill
- poietic-harness-startSkill
- poietic-harness-updateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 9
Start with the project's product requirements, design tokens, established components, and supported platforms.
- Distinctive: line 11
Use the knowledge index and targeted local search to select review criteria relevant to the changed flow.
- Distinctive: line 15
Do not install browser tooling or change unrelated UI merely because this skill is present.
≈ “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 standards
Start with the project's product requirements, design tokens, established components, and supported platforms. Preserve those choices unless the task requests a redesign. These are baseline review practices, not a substitute for the owner's specific visual standards.
Use the knowledge index and targeted local search to select review criteria relevant to the changed flow. Read those criteria and inspect the implementation plus rendered behavior when tooling is available. Consult the memory index only for applicable observed lessons.
Report concrete findings with the affected interaction, evidence, user impact, and a practical correction. Distinguish observed behavior from code-based inference and untested states. Prioritize problems that block or confuse users over stylistic preferences.
Do not install browser tooling or change unrelated UI merely because this skill is present. State which interactions could not be checked. Use the current project's verification tools when available.
Maintain project-specific standards in this component's scoped knowledge/local/ and observed lessons in memory/local/, updating their local indexes with evidence and dates. Keep shared knowledge curated and avoid mixing one project's private details into another scope.
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.