Radix UI Design System

Radix UI Design System

Build production-ready, accessible design systems using Radix UI primitives with full customization control and zero style opinions.

When to Use

• The request matches the skill description: Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.
• The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
• The work would benefit from the complete guidance preserved in references/full-guidance.md.

Core Workflow

1. Confirm the request matches this skill's trigger, scope, and risk profile.
2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

• Overview
• When to Use This Skill
• Do not use this skill when
• Core Principles
• Accessibility First
• Headless Architecture
• Composition Over Configuration
• Getting Started
• Installation
• Basic Component Pattern
• Theming Strategies
• Strategy 1: CSS Variables (Framework-Agnostic)
• Strategy 2: Tailwind + CVA (Class Variance Authority)
• Strategy 3: Stitches (CSS-in-JS)
• Component Patterns
• Pattern 1: Compound Components with Context
• Pattern 2: Polymorphic Components with asChild
• Pattern 3: Controlled vs Uncontrolled

Reference Map

• references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.