agentleFS
Sign inStart free
wpgauravwpgaurav/WordPress-skills/skills/design/ui-skills/SKILL.md

ui-skills

Skill19 starsChanged 23 days agoMITView on GitHub

Opinionated constraints for building better interfaces with agents.

12 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-creator.

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

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    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

42 rules. 7 are common, 11 are distinctive, and 24 are very specific to this project.

  • 7

    Common

    Most of the 9 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 24

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, apply these opinionated constraints for building better interfaces.

    line 12
  2. Distinctive:

    MUST use Tailwind CSS defaults unless custom values already exist or are explicitly requested

    line 27
  3. Very specific:

    MUST use motion/react (formerly framer-motion) when JavaScript animation is required

    line 28
  4. Very specific:

    SHOULD use tw-animate-css for entrance and micro-animations in Tailwind CSS

    line 29
  5. Very specific:

    MUST use cn utility (clsx + tailwind-merge) for class logic

    line 30
  6. Very specific:

    MUST use accessible component primitives for anything with keyboard or focus behavior (Base UI, React Aria, Radix)

    line 34
  7. Distinctive:

    MUST use the project’s existing component primitives first

    line 35
  8. Common:

    NEVER mix primitive systems within the same interaction surface

    line 36
  9. Very specific:

    SHOULD prefer Base UI for new primitives if compatible with the stack

    line 37
  10. Very specific:

    MUST add an aria-label to icon-only buttons

    line 38
  11. Distinctive:

    NEVER rebuild keyboard or focus behavior by hand unless explicitly requested

    line 39
  12. Very specific:

    MUST use an AlertDialog for destructive or irreversible actions

    line 43
  13. Distinctive:

    SHOULD use structural skeletons for loading states

    line 44
  14. Very specific:

    NEVER use h-screen, use h-dvh

    line 45
  15. Very specific:

    MUST respect safe-area-inset for fixed elements

    line 46
  16. Distinctive:

    MUST show errors next to where the action happens

    line 47
  17. Very specific:

    NEVER block paste in input or textarea elements

    line 48
  18. Distinctive:

    NEVER add animation unless it is explicitly requested

    line 52
  19. Very specific:

    MUST animate only compositor props (transform, opacity)

    line 53
  20. Very specific:

    NEVER animate layout properties (width, height, top, left, margin, padding)

    line 54
  21. Very specific:

    SHOULD avoid animating paint properties (background, color) except for small, local UI (text, icons)

    line 55
  22. Very specific:

    SHOULD use ease-out on entrance

    line 56
  23. Very specific:

    NEVER exceed 200ms for interaction feedback

    line 57
  24. Distinctive:

    MUST pause looping animations when off-screen

    line 58
  25. Common:

    NEVER introduce custom easing curves unless explicitly requested

    line 60
  26. Distinctive:

    SHOULD avoid animating large images or full-screen surfaces

    line 61
  27. Very specific:

    MUST use text-balance for headings and text-pretty for body/paragraphs

    line 65
  28. Very specific:

    MUST use tabular-nums for data

    line 66
  29. Very specific:

    SHOULD use truncate or line-clamp for dense UI

    line 67
  30. Very specific:

    NEVER modify letter-spacing (tracking-*) unless explicitly requested

    line 68
  31. Very specific:

    MUST use a fixed z-index scale (no arbitrary z-*)

    line 72
  32. Very specific:

    SHOULD use size-* for square elements instead of w-* + h-*

    line 73
  33. Very specific:

    NEVER animate large blur() or backdrop-filter surfaces

    line 77
  34. Very specific:

    NEVER apply will-change outside an active animation

    line 78
  35. Very specific:

    NEVER use useEffect for anything that can be expressed as render logic

    line 79
  36. Common:

    NEVER use gradients unless explicitly requested

    line 83
  37. Common:

    NEVER use purple or multicolor gradients

    line 84
  38. Common:

    NEVER use glow effects as primary affordances

    line 85
  39. Common:

    SHOULD use Tailwind CSS default shadow scale unless explicitly requested

    line 86
  40. Distinctive:

    MUST give empty states one clear next action

    line 87
  41. Distinctive:

    SHOULD limit accent color usage to one per view

    line 88
  42. Common:

    SHOULD use existing theme or Tailwind CSS color tokens before introducing new ones

    line 89

“Common” is measured: kept by at least 6 in 10 of the 9 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

From ui-skills by Julien Thibeaut (ibelick). Copyright (c) 2026 Julien Thibeaut, used under the MIT License. See NOTICE.md.

UI Skills

When invoked, apply these opinionated constraints for building better interfaces.

How to use

  • /ui-skills
    Apply these constraints to any UI work in this conversation.
  • /ui-skills <file>
    Review the file against all constraints below and output:
    • violations (quote the exact line/snippet)
    • why it matters (1 short sentence)
    • a concrete fix (code-level suggestion)

Stack

  • MUST use Tailwind CSS defaults unless custom values already exist or are explicitly requested
  • MUST use motion/react (formerly framer-motion) when JavaScript animation is required
  • SHOULD use tw-animate-css for entrance and micro-animations in Tailwind CSS
  • MUST use cn utility (clsx + tailwind-merge) for class logic

Components

  • MUST use accessible component primitives for anything with keyboard or focus behavior (Base UI, React Aria, Radix)
  • MUST use the project’s existing component primitives first
  • NEVER mix primitive systems within the same interaction surface
  • SHOULD prefer Base UI for new primitives if compatible with the stack
  • MUST add an aria-label to icon-only buttons
  • NEVER rebuild keyboard or focus behavior by hand unless explicitly requested

Interaction

  • MUST use an AlertDialog for destructive or irreversible actions
  • SHOULD use structural skeletons for loading states
  • NEVER use h-screen, use h-dvh
  • MUST respect safe-area-inset for fixed elements
  • MUST show errors next to where the action happens
  • NEVER block paste in input or textarea elements

Animation

  • NEVER add animation unless it is explicitly requested
  • MUST animate only compositor props (transform, opacity)
  • NEVER animate layout properties (width, height, top, left, margin, padding)
  • SHOULD avoid animating paint properties (background, color) except for small, local UI (text, icons)
  • SHOULD use ease-out on entrance
  • NEVER exceed 200ms for interaction feedback
  • MUST pause looping animations when off-screen
  • SHOULD respect prefers-reduced-motion
  • NEVER introduce custom easing curves unless explicitly requested
  • SHOULD avoid animating large images or full-screen surfaces

Typography

  • MUST use text-balance for headings and text-pretty for body/paragraphs
  • MUST use tabular-nums for data
  • SHOULD use truncate or line-clamp for dense UI
  • NEVER modify letter-spacing (tracking-*) unless explicitly requested

Layout

  • MUST use a fixed z-index scale (no arbitrary z-*)
  • SHOULD use size-* for square elements instead of w-* + h-*

Performance

  • NEVER animate large blur() or backdrop-filter surfaces
  • NEVER apply will-change outside an active animation
  • NEVER use useEffect for anything that can be expressed as render logic

Design

  • NEVER use gradients unless explicitly requested
  • NEVER use purple or multicolor gradients
  • NEVER use glow effects as primary affordances
  • SHOULD use Tailwind CSS default shadow scale unless explicitly requested
  • MUST give empty states one clear next action
  • SHOULD limit accent color usage to one per view
  • SHOULD use existing theme or Tailwind CSS color tokens before introducing new ones

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.

Check your setup, free