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
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 (Radix UI)
MUST use the project’s existing component primitives first
NEVER mix primitive systems within the same interaction surface
SHOULD prefer shadcn-vue 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
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
1---2name: baseline-ui3description: Baseline UI4---5# Baseline UI67Enforces an opinionated UI baseline to prevent AI-generated interface slop.89## How to use1011- `/baseline-ui`12 Apply these constraints to any UI work in this conversation.1314- `/baseline-ui <file>`15 Review the file against all constraints below and output:16 - violations (quote the exact line/snippet)17 - why it matters (1 short sentence)18 - a concrete fix (code-level suggestion)1920## Stack2122- MUST use Tailwind CSS defaults unless custom values already exist or are explicitly requested23- SHOULD use `tw-animate-css` for entrance and micro-animations in Tailwind CSS24- MUST use `cn` utility (`clsx` + `tailwind-merge`) for class logic2526## Components2728- MUST use accessible component primitives for anything with keyboard or focus behavior (`Radix UI`)29- MUST use the project’s existing component primitives first30- NEVER mix primitive systems within the same interaction surface31- SHOULD prefer [`shadcn-vue`](https://www.shadcn-vue.com/docs/components) for new primitives if compatible with the stack32- MUST add an `aria-label` to icon-only buttons33- NEVER rebuild keyboard or focus behavior by hand unless explicitly requested3435## Interaction3637- MUST use an `AlertDialog` for destructive or irreversible actions38- SHOULD use structural skeletons for loading states39- NEVER use `h-screen`, use `h-dvh`40- MUST respect `safe-area-inset` for fixed elements41- MUST show errors next to where the action happens42- NEVER block paste in `input` or `textarea` elements4344## Animation4546- NEVER add animation unless it is explicitly requested47- MUST animate only compositor props (`transform`, `opacity`)48- NEVER animate layout properties (`width`, `height`, `top`, `left`, `margin`, `padding`)49- SHOULD avoid animating paint properties (`background`, `color`) except for small, local UI (text, icons)50- SHOULD use `ease-out` on entrance51- NEVER exceed `200ms` for interaction feedback52- MUST pause looping animations when off-screen53- SHOULD respect `prefers-reduced-motion`54- NEVER introduce custom easing curves unless explicitly requested55- SHOULD avoid animating large images or full-screen surfaces5657## Typography5859- MUST use `text-balance` for headings and `text-pretty` for body/paragraphs60- MUST use `tabular-nums` for data61- SHOULD use `truncate` or `line-clamp` for dense UI62- NEVER modify `letter-spacing` (`tracking-*`) unless explicitly requested6364## Layout6566- MUST use a fixed `z-index` scale (no arbitrary `z-*`)67- SHOULD use `size-*` for square elements instead of `w-*` + `h-*`6869## Performance7071- NEVER animate large `blur()` or `backdrop-filter` surfaces72- NEVER apply `will-change` outside an active animation7374## Design7576- NEVER use gradients unless explicitly requested77- NEVER use purple or multicolor gradients78- NEVER use glow effects as primary affordances79- SHOULD use Tailwind CSS default shadow scale unless explicitly requested80- MUST give empty states one clear next action81- SHOULD limit accent color usage to one per view82- SHOULD use existing theme or Tailwind CSS color tokens before introducing new ones
Run npx skillmds@latest add comeonoliver/baseline-ui in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Baseline UI It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.