baseline-ui
Ensures UI quality and accessibility by enforcing opinionated design standards and component patterns.
Install
mkdir -p .claude/skills/baseline-ui && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4083" && unzip -o skill.zip -d .claude/skills/baseline-ui && rm skill.zipInstalls to .claude/skills/baseline-ui
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Enforces an opinionated UI baseline to prevent AI-generated interface slop.Key capabilities
- →Audits UI files against strict accessibility constraints
- →Flags non-accessible icon-only buttons
- →Detects improper loading state implementations
- →Identifies non-standard border color usage
- →Enforces compositor-only animations
How it works
Runs a static analysis check against a predefined set of design rules and accessibility patterns, comparing the target file's code structure to required primitives.
Inputs & outputs
When to use baseline-ui
- →Audit UI code for design compliance
- →Apply standard styling to new features
- →Fix accessibility violations
About this skill
Baseline UI
Enforces an opinionated UI baseline to prevent AI-generated interface slop.
How to use
-
/baseline-uiApply 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 (spacing, radius, shadows) before custom values
- 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 (
Radix) - MUST use the project’s existing component primitives first
- NEVER mix primitive systems within the same interaction surface
- MUST add an
aria-labelto icon-only buttons - NEVER rebuild keyboard or focus behavior by hand unless explicitly requested
- MUST use
isLoadingprop on theButtoncomponent when indicating loading state - NEVER use
ml-xormr-xwhen styling an icon inside a button, since spacing will be given to it automatically - NEVER explicitly set border color to
border-bordersince this is the default border color
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
- MUST 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-x) - SHOULD use
size-xfor square elements instead ofw-x+h-x - SHOULD use
gap-*for spacing between elements instead ofspace-x-*orspace-y-*(with appropriateflexandflex-directionclasses)
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
When not to use it
- →Visualizing complex non-standard UI experiments
- →Projects requiring legacy custom component libraries
Prerequisites
Limitations
- →Requires Radix primitives for interaction behavior
- →Cannot resolve complex dynamic state dependencies
- →Strictly forbids non-compositor animations
How it compares
Unlike a general prompt, this strictly enforces project-wide design compliance through automated lint-like evaluation.
Compared to similar skills
baseline-ui side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| baseline-ui (this skill) | 3 | 6mo | No flags | Intermediate |
| web-design-reviewer | 7 | 7mo | No flags | Intermediate |
| bencium-innovative-ux-designer | 1 | 5mo | No flags | Advanced |
| theme-system | 1 | 25d | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by agentset-ai
View all by agentset-ai →You might also like
web-design-reviewer
github
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.
bencium-innovative-ux-designer
bencium
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
theme-system
btriapitsyn
Use when creating or modifying UI components, styling, or visual elements in OpenChamber. All UI colors must use theme tokens - never hardcoded values or Tailwind color classes.
frontend-system
ZroZoom
UI/UX expert. Use for creating components, styling (Tailwind), accessibility, and translations (I18n). Trigger when: create a component, change appearance, add a chart, translate, stwórz komponent, zmień wygląd, dodaj wykres, przetłumacz.
ui-skills
Ktasl
Apply strict, opinionated UI constraints to any UI work (React/Tailwind) in this conversation.
userinterface-wiki
raphaelsalaja
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.