
Baseline Ui
- 17.1k installs
- 6.9k repo stars
- Updated August 3, 2026
- ibelick/ui-skills
Baseline UI is a skill for enforcing design constraints and eliminating UI code slop through Tailwind CSS, accessibility rules, and animation patterns.
About
Baseline UI enforces opinionated UI design constraints to eliminate AI-generated interface slop through spacing, hierarchy, typography, and animation rules. It mandates Tailwind CSS defaults, motion/react for animations on compositor properties only, accessible component primitives (Base UI, React Aria, Radix), and typography best practices like text-balance for headings and tabular-nums for data. Use this skill when polishing interfaces, reviewing UI code for anti-patterns, or establishing design system compliance. Includes performance guardrails, animation timing budgets (max 200ms), and safe-area-inset handling for fixed elements.
- Tailwind CSS baseline enforcement with motion/react animations
- Accessible component primitives (Base UI, React Aria, Radix) integration
- Animation constraints (compositor-only, max 200ms) and typography rules (text-balance, tabular-nums)
Baseline Ui by the numbers
- 17,126 all-time installs (skills.sh)
- +387 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #43 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
baseline-ui capabilities & compatibility
- Use cases
- ui design · frontend
- Platforms
- macOS · Windows · Linux
- Runs
- Runs locally
- Pricing
- Free
npx skills add https://github.com/ibelick/ui-skills --skill baseline-uiAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17.1k |
|---|---|
| repo stars | ★ 6.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 3, 2026 |
| Repository | ibelick/ui-skills ↗ |
How do you enforce Tailwind UI consistency in AI-generated components?
Baseline UI enforces opinionated UI design constraints to eliminate AI-generated interface slop through spacing, hierarchy, typography, and animation rules. It mandates Tailwind CSS defaults, motion/
Who is it for?
Frontend developers building Tailwind CSS React components who need automated checks against animation, typography, accessibility, and layout anti-patterns.
Skip if: Teams not using Tailwind CSS or developers who only need full visual design systems rather than utility-class constraint enforcement.
When should I use this skill?
User is building or reviewing Tailwind UI components, styling React views, or asks to prevent AI-generated interface slop.
What you get
Violation report with quoted snippets, rationale per issue, and concrete Tailwind/CSS fix suggestions.
- polished ui code
- accessibility compliance
- performance-optimized animations
By the numbers
- Covers 4 constraint areas: animation durations, typography scale, accessibility, and layout anti-patterns
Files
Baseline UI
Enforces an opinionated UI baseline to prevent AI-generated interface slop.
How to use
/baseline-ui
Apply these constraints to any UI work in this conversation.
/baseline-ui <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(formerlyframer-motion) when JavaScript animation is required - SHOULD use
tw-animate-cssfor entrance and micro-animations in Tailwind CSS - MUST use
cnutility (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-labelto icon-only buttons - NEVER rebuild keyboard or focus behavior by hand unless explicitly requested
Interaction
- MUST use an
AlertDialogfor destructive or irreversible actions - SHOULD use structural skeletons for loading states
- NEVER use
h-screen, useh-dvh - MUST respect
safe-area-insetfor fixed elements - MUST show errors next to where the action happens
- NEVER block paste in
inputortextareaelements
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-outon entrance - NEVER exceed
200msfor 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-balancefor headings andtext-prettyfor body/paragraphs - MUST use
tabular-numsfor data - SHOULD use
truncateorline-clampfor dense UI - NEVER modify
letter-spacing(tracking-*) unless explicitly requested
Layout
- MUST use a fixed
z-indexscale (no arbitraryz-*) - SHOULD use
size-*for square elements instead ofw-*+h-*
Performance
- NEVER animate large
blur()orbackdrop-filtersurfaces - NEVER apply
will-changeoutside an active animation - NEVER use
useEffectfor 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
Related skills
Forks & variants (2)
Baseline Ui has 2 known copies in the catalog totaling 75 installs. They canonicalize to this original listing.
How it compares
Pick baseline-ui over generic lint rules when you need opinionated Tailwind-specific UI baseline enforcement with quoted violations and fix suggestions.
FAQ
What animation properties should I use?
Only animate compositor properties (transform, opacity). Never animate layout (width, height, margin, padding) or paint properties (background, color) except for small UI elements.
Which component primitives are recommended?
Use Base UI, React Aria, or Radix for keyboard/focus behavior. Never mix primitive systems in the same interaction surface. Always add aria-label to icon-only buttons.
Is Baseline Ui safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.