baseline-ui

Reviews and fixes UI code against spacing, typography, animation, and accessibility constraints.

Updated Aug 8, 2026
One-click install
npx skills add https://github.com/wolfstar-project/code-zero --skill baseline-ui-wolfstar-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: baseline-ui
Source: https://github.com/wolfstar-project/code-zero/tree/main/.agents/skills/baseline-ui
Command: npx skills add https://github.com/wolfstar-project/code-zero --skill baseline-ui-wolfstar-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interface code often ships with inconsistent spacing, broken hierarchy, inaccessible components, and gratuitous animations. This Skill enforces an opinionated UI baseline so every interface pass meets consistent quality constraints. ## Core Features & Use Cases - Constraint Enforcement: Applies strict rules for Tailwind CSS usage, component primitives (Base UI, React Aria, Radix), animation limits, typography, layout, and performance. - File Review Mode: Audits a specific file and reports violations with the exact offending snippet, a one-sentence rationale, and a concrete code-level fix. - Use Case: After generating a new dashboard page, run a baseline review to catch issues like h-screen instead of h-dvh, missing aria-label on icon buttons, or animations exceeding 200ms before merging. ## Quick Start Ask the AI to review your UI file against the baseline-ui constraints and list every violation with a concrete fix.

Frequently Asked Questions about baseline-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a React component file for UI quality issues?▼

Invoke the baseline-ui review on the target file to get a list of violations quoting the exact snippet, a one-sentence explanation of why each matters, and a concrete code-level fix for spacing, typography, animation, and accessibility problems.

What component primitives should I use for accessible React UI?▼

Use accessible primitives such as Base UI, React Aria, or Radix for anything with keyboard or focus behavior, preferring the project's existing primitives first. Never mix primitive systems within the same interaction surface or rebuild focus handling by hand.

Which CSS properties are safe to animate in web interfaces?▼

Animate only compositor properties like transform and opacity. Never animate layout properties such as width, height, top, left, margin, or padding, and keep interaction feedback under 200ms with ease-out timing on entrances.

Should I use h-screen or h-dvh for full-height layouts?▼

Use h-dvh instead of h-screen, since dynamic viewport height accounts for mobile browser chrome. Fixed elements must also respect safe-area-inset so content is not obscured by device notches or system UI.

When should animations not be added to a UI?▼

Never add animation unless explicitly requested. When used, pause looping animations off-screen, respect prefers-reduced-motion, avoid animating large blur or backdrop-filter surfaces, and never apply will-change outside an active animation.