Agent skill

Baseline UI Skill for Cleaner AI-Built Interfaces

The baseline-ui skill from ibelick/ui-skills gives an AI coding agent a list of MUST, SHOULD and NEVER rules for Tailwind interfaces, animation, accessibility and layout.

Install
git clone https://github.com/ibelick/ui-skills.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the baseline-ui skill?

Baseline-ui is a skill in the ibelick/ui-skills repository. It gives an AI coding agent opinionated rules for building interfaces with Tailwind, motion and accessible primitives, and it can audit a file and list violations with a reason and a concrete fix for each one.

It is a skill in the ibelick/ui-skills repository that acts as a rulebook for interface code. It has two modes. Running /baseline-ui applies the rules while the agent builds, and /baseline-ui followed by a file path audits that file and lists each violation with why it matters and a concrete fix.

What changes in your agent's output

  • Stack: Tailwind defaults, motion/react, tw-animate-css and a cn helper.
  • Components: accessible primitives such as Base UI, React Aria or Radix, an aria-label on icon buttons, and never a mix of primitive systems.
  • Interaction: AlertDialog for destructive actions, skeletons while loading, h-dvh instead of h-screen, safe-area-inset support and never blocking paste.
  • Animation: none unless requested, compositor properties only, 200ms or less, ease-out entrances, reduced motion respected and off-screen loops paused.
  • Typography: text-balance, text-pretty and tabular-nums, with no tracking changes.

More rules in the skill

  • Layout: a fixed z-index scale and size-* for equal width and height.
  • Performance: no large blur surfaces, will-change only during an animation, and no useEffect for render logic.
  • Design: no gradients, and never purple or multicolor ones, no glow, one accent color per view and empty states with one next action.

Who the skill is for

Best for

  • React and Tailwind projects where AI-generated screens drift toward generic, gradient-heavy styling.
  • Teams that want a pre-merge audit of a component with fixes attached.
  • Developers who prefer firm rules to open-ended taste guidance.

Not for

  • Projects without Tailwind or React, since many rules assume that stack.
  • Work that needs expressive gradients or glow, which the skill forbids.
  • Native mobile code. Use a native mobile skill instead.

Pair it with polish for a final pass and improve-ui for redesigns. To record your own rules for an agent, see create-design-md.