ui-ux
Skill0 starsChanged 20 days agoMITView on GitHub
Use when you write or change UI code or look: screens, layouts, Jetpack Compose or XML views, themes, colors, type, spacing, icons, animations, dialogs, or any request about how an app looks or feels. Android first, also web and desktop.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- kv0906/cc-skillstheir own version, first seen Nov 8, 2026
- whoamnesia/astudio-aiotheir own version, first seen Nov 8, 2026
- turkeryildirim/ai-skillstheir own version, first seen Nov 1, 2026
- prinx/agentstheir own version, first seen Oct 20, 2026
- psubramanian/Claude-Skillstheir own version, first seen Oct 13, 2026
- zoharp/claude-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use deploy.
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.
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- kv0906/cc-skills★ 42same name
- prangishviliAbe/agent-skills★ 8same name
- turkeryildirim/ai-skills★ 4same name
- hiteshbandhu/skills-i-use★ 1same name
- whoamnesia/astudio-aio★ 1same name
- asv-digital/skills-claude-code-na-pratica★ 0same name
- prinx/agents★ 0same name
- psubramanian/Claude-Skills★ 0same name
- Sean-Michael/skills★ 0same name
- zoharp/claude-skills★ 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 repository6 other files it gives its agents.
- asd-ste100Skill
- audit-repoSkill
- audit-uiSkill
- ooga-boggaSkill
- session-endSkill
- yagniSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Follow the platform: Material 3 on Android, the native style on iOS and desktop.
- Distinctive: line 13
Read 2 sibling screens. Copy their spacing, type, colors, radii and components.
- Distinctive: line 14
If a value is missing, add it to the shared tokens first.
- Distinctive: line 15
When you change a shared value, check every screen that uses it.
- Distinctive: line 18
Put the main item at the top and leading side.
- Distinctive: line 19
Use one spacing scale (4 dp steps).
- Distinctive: line 20
Use at most 2 type sizes per area and 1 accent color.
- Distinctive: line 33
Every icon button has a label or content description.
- Distinctive: line 40
Every state change has a transition.
- Distinctive: line 41
Do not use motion as the only signal.
- Distinctive: line 45
Use vector icons in one style.
- Distinctive: line 46
Use a verb on a button: "Save", not "OK".
- Very specific: line 49
Run the UI at the smallest and largest size.
“Common” is measured: kept by at least 6 in 10 of the 7 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
UI/UX
Follow the platform: Material 3 on Android, the native style on iOS and desktop. Do not copy a web pattern into an app. Values are in references/platforms.md.
Before you build
- Name the one job of the screen. Make that action the most visible item.
- Find the shared tokens (theme, colors, type, spacing, shapes, motion) and the shared components. Read them first.
- Read 2 sibling screens. Copy their spacing, type, colors, radii and components.
- If a value is missing, add it to the shared tokens first. Then use it. Do not write a literal color, size or duration in a screen.
- When you change a shared value, check every screen that uses it.
Layout
- Put the main item at the top and leading side. Hide secondary choices in menus or nested views.
- Use one spacing scale (4 dp steps). Group related items with space, not lines.
- Use at most 2 type sizes per area and 1 accent color. Color shows state, not decoration.
- Respect safe areas, the keyboard and system bars. Keep the same functions at every window size.
- Touch target: 48 dp or more. Pointer target: 32 px or more.
States
- Build all states: default, pressed, focus, disabled, loading, empty, error.
- Show progress for any action over 300 ms.
- An error says what failed and what to do. Never show a raw code alone.
- Disable or hide an action that cannot work. Say why.
Access
- Contrast 4.5:1 for text, 3:1 for large text, icons and borders. Check light and dark.
- Color is never the only signal: add an icon, shape or label.
- Every icon button has a label or content description.
- Text grows to 200 percent without cropping. Use sp units and let rows grow.
- Respect dark mode, font scale and reduced motion.
Motion
- Define each animation once, by role: press, toggle, screen enter, screen exit, list item, dialog. Search for the role and reuse it.
- On a screen change, lay out the final content first. Then run one animation. Do not refresh during it. Do not stack two transitions.
- Every state change has a transition. A snap is a bug.
- Do not use motion as the only signal. Reduce Motion replaces slides with fades.
Rendering and words
- Clip a rounded shape with its own radius. No square background behind it.
- Use vector icons in one style. Never stretch a low-resolution image.
- Use a verb on a button: "Save", not "OK". One name for one thing.
Check
Run the UI at the smallest and largest size. Report what you saw, not what you intended. For a full audit, the user types /audit-ui.
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.

