baseline-ui

Enforce Tailwind defaults and accessible primitives for consistent UI.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/kimmyxpow/focus --skill baseline-ui-kimmyxpow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baseline-ui
Source: https://github.com/kimmyxpow/focus/tree/main/.claude/skills/baseline-ui
Command: npx skills add https://github.com/kimmyxpow/focus --skill baseline-ui-kimmyxpow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces an opinionated UI baseline to prevent AI-generated interface slop.

Core Features & Use Cases

  • Enforces consistent UI patterns across components and screens.
  • Improves accessibility and keyboard focus handling by standardizing primitives.
  • Reduces design drift by enforcing a single source of truth for tokens, layout, and interaction rules.

Quick Start

Apply the baseline-ui constraints to your UI work by integrating into your design system workflow, for example: baseline-ui apply --project <project-name>.

Frequently Asked Questions about baseline-ui

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

FAQPage Schema
How do I prevent AI-generated UI slop in React projects?

Preventing AI-generated UI slop requires enforcing an opinionated UI baseline that standardizes Tailwind defaults, accessible primitives, and a single source of truth for design tokens, layout rules, and interaction patterns.

What's the best way to maintain UI consistency across Tailwind components?

The best way to maintain UI consistency is enforcing a single source of truth for design tokens, layout, and interaction rules alongside standardizing accessible primitives to reduce design drift across components and screens.

How do I standardize accessibility and keyboard focus handling in frontend design systems?

Standardizing accessibility and keyboard focus handling in frontend design systems involves enforcing accessible primitives and a dependable UI baseline to curb slop, ensuring consistent interaction patterns across all components.

Does baseline-ui require specific dependencies to apply its design system constraints?

No specific dependencies are required to apply the baseline-ui design system constraints, as the Skill operates independently to enforce Tailwind defaults and accessible primitives without external component libraries.

How do I integrate baseline constraints into an existing design system workflow?

You integrate baseline constraints by applying them to your design system workflow using commands like 'baseline-ui apply --project <project-name>' to enforce consistent UI patterns across your components and screens.