Refined UI

An opinionated, customizable superset of shadcn/ui

AgentsPrimitivesSkillsSkins
Guides
  • Overview
  • Get started
  • Shadcn compatibility
  • Architecture
  • Agent surface
CSS-first
  • CSS-first interactivity
  • CSS-first motion & sizing
React code quality
  • Derive, do not duplicate
  • Remount state boundaries
  • One responsibility per file
  • Real stack tests
UI / Tailwind
  • Use existing components first
  • Token discipline
  • Class Name boundaries
  • Tailwind v4 CSS configuration
  • Tailwind v4 migration syntax
  • Generated utilities before arbitrary values
  • Variant-first styling
  • Tailwind v4 capabilities
  • Tailwind v4 behavior & motion
UX
  • State continuity
  • Provenance without noise
  • Dense but scannable
  • Say it once
Refined UI registry
  • Skin authoring
  • Extension authoring
  • Registry-first DX
  • Skin completeness
  • Refined UI composition
  • Runtime-agnostic UI
  • Compound components DX
  • Context vs props
  1. Skills
  3. Token discipline
Skill / UI / Tailwind

Token discipline

Use established design tokens and local CSS variables before reaching for one-off values.

Goal

Keep the visual language themeable and predictable by styling through approved tokens.

Styling rules for Tailwind v4, token discipline, component reuse, and className boundaries.

Checks

1Prefer existing color, spacing, radius, shadow, and typography tokens.
2Introduce local CSS variables only when a component needs a named internal scale.
3Keep arbitrary values exceptional and constrained to precise dimensions when no token fits.

Avoid

1Changing shared Tailwind tokens as part of a narrow component task.
2Sprinkling arbitrary color, shadow, spacing, or radius values across product code.

Source

Imported as local Refined UI skill guidance, with this repo owning the final wording.

Mastra tailwind-v4
../mastra/.claude/skills/tailwind-v4

On this page

  • Checks
  • Avoid
  • Source