baseline-ui

Enforce typography, animation, accessibility, and layout constraints for Tailwind-based React interfaces.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/brp00005/site2 --skill baseline-ui-brp00005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baseline-ui
Source: https://github.com/brp00005/site2/tree/main/.cursor/skills/baseline-ui
Command: npx skills add https://github.com/brp00005/site2 --skill baseline-ui-brp00005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a consistent UI standard to reduce visual drift, accessibility gaps, and subjective design decisions across Tailwind-based interfaces.

Core Features & Use Cases

  • Typography scale enforcement to ensure headings and body text stay on-pattern across components.
  • Accessibility primitives and ARIA labeling to promote usable, keyboard-navigable interfaces.
  • Adherence to Tailwind defaults and design tokens to maintain visual coherence across products.

Quick Start

Apply baseline-ui to your UI work and begin validating components against the baseline rules.

Frequently Asked Questions about baseline-ui

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

FAQPage Schema
How do I enforce a consistent UI baseline in React and Tailwind?

To enforce a consistent UI baseline in React and Tailwind, you need a system that codifies typography, animation, accessibility, and layout constraints. This reduces visual drift and subjective design decisions across your interface components.

What's the best way to standardize typography and accessibility primitives?

Standardize typography and accessibility primitives by enforcing a consistent scale for headings and body text alongside ARIA labeling for icon buttons. This promotes usable, keyboard-navigable interfaces while maintaining visual coherence across products.

Does this UI baseline approach work with default Tailwind design tokens?

Yes, this UI baseline approach works with default Tailwind design tokens. It specifically relies on Tailwind defaults and design tokens to maintain visual coherence, guiding developers to validate components against these baseline rules during design reviews.

How do I validate frontend codebases against UI accessibility and animation rules?

Validate frontend codebases against UI accessibility and animation rules by applying codified constraints to your UI components. This checks for ARIA labeling, controlled animation behavior, and adherence to Tailwind defaults during your standard component design reviews.

Why does visual drift occur in Tailwind-based interfaces and how do I reduce it?

Visual drift occurs in Tailwind-based interfaces due to accessibility gaps and subjective design decisions. You reduce it by establishing a consistent UI standard that enforces typography scale, accessible primitives, and layout constraints across all components.