agentleFS
davidvornholtdavidvornholt/mailbox/.agents/skills/ux-ui/SKILL.md

ux-ui

Skill2 starsChanged 11 days agoMITView on GitHub

Use when creating or changing a user-facing interface. Applies the project's styling, component placement, theme, icon, and accessibility-test conventions.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Lucide (lucide-react) for icons in React interfaces.

    line 14

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

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

UX/UI

Style with Tailwind utilities in the markup. When UI repeats, share it as a component with variants rather than an @apply class. Custom CSS is fine where utilities would obscure the intent.

Shared UI goes in src/shared/ui within an app and in packages/ui across apps.

Components use the app theme's semantic tokens rather than raw palette values. Author theme colors in oklch(...).

Use Lucide (lucide-react) for icons in React interfaces.

Browser-rendered apps check accessibility with Playwright and @davidvornholt/a11y-testing, which provides the axe scanner and the shared Playwright configuration. Each app lists the routes and UI states it scans in a11y/*.a11y.ts. When a change adds or alters a route or a meaningful UI state, update its coverage there.

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.