baseline-ui

Enforce Tailwind defaults and accessible component constraints in UI reviews.

116|9|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill baseline-ui-elophanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baseline-ui
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/baseline-ui
Command: npx skills add https://github.com/elophanto/EloPhanto --skill baseline-ui-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces an opinionated UI baseline to prevent AI-generated interface slop.

Core Features & Use Cases

  • Tailwind defaults compliance for UI consistency
  • Accessible component primitives and design-system-first approach
  • Review and enforce UI quality during development and design sprints

Quick Start

Apply baseline-ui constraints to the current UI work in this conversation.

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 frontend components?

You prevent UI slop by applying an opinionated UI baseline that constrains AI generation with Tailwind defaults, accessible component primitives, and structured motion rules. This enforces UI consistency and stops low-quality interface output.

What is a UI baseline and how does it enforce design system consistency?

A UI baseline is a set of structured design rules that enforces consistency by specifying constraints like Tailwind defaults and accessible component primitives. It acts as a strict standard to review and maintain UI quality during development sprints.

How do I apply UI consistency constraints to a Tailwind project?

You apply UI consistency constraints to a Tailwind project by enforcing Tailwind defaults and accessible component primitives within your workflow. This ensures generated interfaces adhere to a structured design system and maintain quality.

Can I use baseline-ui for UI review workflows during design sprints?

Yes, you can use this approach for UI review workflows during design sprints. It enforces UI quality by checking interfaces against structured design rules, Tailwind defaults, and accessible component constraints to prevent interface slop.

Do I need a predefined design system to enforce accessible component primitives?

You do not need an external design system package, as the baseline itself provides accessible component primitives and design-system-first rules. It specifies the exact constraints required to maintain accessible and consistent frontend components.