Agent skill · Frontend

radix-ui-design-system

Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill radix-ui-design-system --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 22 KB
Bundled scripts: none
Path: skills/radix-ui-design-system/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Radix UI Design System Build production-ready, accessible design systems using Radix UI primitives with full customization control and zero style opinions. ## Overview Radix UI provides unstyled, accessible components (primitives) that you can customize to match any design system. This skill guides you through building scalable component libraries with Radix UI, focusing on accessibility-first design, theming architecture, and composable patterns. **Key Strengths:** - **Headless by design**: Full styling control without fighting defaults - **Accessibility built-in**: WAI-ARIA compliant, keyboard navigation, screen reader support - **Composable primitives**: Build complex components from simple building blocks - **Framework agnostic**: Works with React, but styles work anywhere ## When to Use This Skill - Creating a custom design system from scratch - Building accessible UI component libraries - Implementing complex interactive components (Dialog, Dropdown, Tabs, etc.) - Migrating from styled component libraries to unstyled primitives - Setting up theming systems with CSS variables or Tailwind - Need full control over component behavior and styling - Building applications requirin

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Do not use this skill when
  4. Core Principles
  5. 1. Accessibility First
  6. 2. Headless Architecture
  7. 3. Composition Over Configuration
  8. Getting Started
  9. Installation
  10. Basic Component Pattern
  11. Theming Strategies
  12. Strategy 1: CSS Variables (Framework-Agnostic)
  13. Strategy 2: Tailwind + CVA (Class Variance Authority)
  14. Strategy 3: Stitches (CSS-in-JS)
Ships with 4 files
  • examples/README.md
  • examples/dialog-example.tsx
  • examples/dropdown-example.tsx
  • templates/component-template.tsx.template
Commands it runs
Install individual primitives (recommended)
npm install @radix-ui/react-dialog @radix-ui/react-dropdown-menu
Or install multiple at once
npm install @radix-ui/react-{dialog,dropdown-menu,tabs,tooltip}
For styling (optional but common)
npm install clsx tailwind-merge class-variance-authority
npx shadcn@latest init
npx shadcn@latest add dialog
npm install @radix-ui/react-{primitive-name}
More from agentic-awesome-skills
All skills →
About this skill
What does the radix-ui-design-system skill do?

Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill radix-ui-design-system --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going