agentleFS
spizganedspizganed/skills/ui-ux/SKILL.md

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

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.
  • VercelSkill

    deploy

    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

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
  1. Very specific:

    Follow the platform: Material 3 on Android, the native style on iOS and desktop.

    line 8
  2. Distinctive:

    Read 2 sibling screens. Copy their spacing, type, colors, radii and components.

    line 13
  3. Distinctive:

    If a value is missing, add it to the shared tokens first.

    line 14
  4. Distinctive:

    When you change a shared value, check every screen that uses it.

    line 15
  5. Distinctive:

    Put the main item at the top and leading side.

    line 18
  6. Distinctive:

    Use one spacing scale (4 dp steps).

    line 19
  7. Distinctive:

    Use at most 2 type sizes per area and 1 accent color.

    line 20
  8. Distinctive:

    Every icon button has a label or content description.

    line 33
  9. Distinctive:

    Every state change has a transition.

    line 40
  10. Distinctive:

    Do not use motion as the only signal.

    line 41
  11. Distinctive:

    Use vector icons in one style.

    line 45
  12. Distinctive:

    Use a verb on a button: "Save", not "OK".

    line 46
  13. Very specific:

    Run the UI at the smallest and largest size.

    line 49

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.