ui-components

yonatangross/orchestkit · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/yonatangross/orchestkit --skill ui-components
0 commentsdiscussion
summary

Comprehensive patterns for building accessible UI component libraries with shadcn/ui and Radix Primitives. Covers CVA variants, OKLCH theming, cn() utility, component extension, asChild composition, dialog/menu patterns, and data-attribute styling. Each category has individual rule files in rules/ loaded on-demand.

skill.md

UI Components

Comprehensive patterns for building accessible UI component libraries with shadcn/ui and Radix Primitives. Covers CVA variants, OKLCH theming, cn() utility, component extension, asChild composition, dialog/menu patterns, and data-attribute styling. Each category has individual rule files in rules/ loaded on-demand.

Quick Reference

Category Rules Impact When to Use
shadcn/ui 3 HIGH CVA variants, component customization, form patterns, data tables
Radix Primitives 3 HIGH Dialogs, polymorphic composition, data-attribute styling
Design System 5 HIGH W3C tokens, OKLCH theming, spacing scales, typography, component states, animation
Design System Components 1 HIGH Atomic design, CVA variants, accessibility, Storybook
Forms 2 HIGH React Hook Form v7, Zod validation, Server Actions
Modern CSS & Tooling 3 HIGH CSS cascade layers, Tailwind v4, Storybook CSF3
UX Foundations 4 HIGH Visual hierarchy, typography thresholds, color system, empty states

Total: 21 rules across 7 categories

Quick Start

// CVA variant system with cn() utility
import { cva, type VariantProps } from 'class-variance-authority'
import { cn } from '@/lib/utils'

const buttonVariants = cva(
  'inline-flex items-center justify-center rounded-md font-medium transition-colors',
  {
    variants: {
      variant: {
        default: 'bg-primary text-primary-foreground hover:bg-primary/90',
        destructive: 'bg-destructive text-destructive-foreground',
        outline: 'border border-input bg-background hover:bg-accent',
        ghost: 'hover:bg-accent hover:text-accent-foreground',
      },
      size: {
        default: 'h-10 px-4 py-2',
        sm: 'h-9 px-3',
        lg: 'h-11 px-8',
      },
    },
    defaultVariants: { variant: 'default', size: 'default' },
  }
)
// Radix Dialog with asChild composition
import { Dialog } from 'radix-ui'

<Dialog.Root>
  <Dialog.Trigger asChild>
    <Button>Open</Button>
  </Dialog.Trigger>
  <Dialog.Portal>
    <Dialog.Overlay className="fixed inset-0 bg-black/50" />
    <Dialog.Content className="data-[state=open]:animate-in">
      <Dialog.Title>Title</Dialog.Title>
      <Dialog.Description>Description</Dialog.Description>
      <Dialog.Close>Close</Dialog.Close>
    </Dialog.Content>
  </Dialog.Portal>
</Dialog.Root>

shadcn/ui

Beautifully designed, accessible components built on CVA variants, cn() utility, and OKLCH theming.

Rule File Key Pattern
Customization rules/shadcn-customization.md CVA variants, cn() utility, OKLCH theming, component extension
Forms rules/shadcn-forms.md Form field wrappers, react-hook-form integration, validation
Data Table rules/shadcn-data-table.md TanStack Table integration, column definitions, sorting/filtering

Radix Primitives

Unstyled, accessible React primitives for building high-quality design systems.

Rule File Key Pattern
Dialog rules/radix-dialog.md Dialog, AlertDialog, controlled state, animations
Composition rules/radix-composition.md asChild, Slot, nested triggers, polymorphic rendering
Styling rules/radix-styling.md Data attributes, Tailwind arbitrary variants, focus management

Key Decisions

Decision Recommendation
Color format OKLCH for perceptually uniform theming
Class merging Always use cn() for Tailwind conflicts
Extending components Wrap, don't modify source files
Variants Use CVA for type-safe multi-axis variants
Styling approach Data attributes + Tailwind arbitrary variants
Composition Use asChild to avoid wrapper divs
Animation CSS-only with data-state selectors
Form components Combine with react-hook-form

Anti-Patterns (FORBIDDEN)

  • Modifying shadcn source: Wrap and extend instead of editing generated files
  • Skipping cn(): Direct string concatenation causes Tailwind class conflicts
  • Inline styles over CVA: Use CVA for type-safe, reusable variants
  • Wrapper divs: Use asChild to avoid extra DOM elements
  • Missing Dialog.Title: Every dialog must have an accessible title
  • Positive tabindex: Using tabindex > 0 disrupts natural tab order
  • Color-only states: Use data attributes + multiple indicators
  • Manual focus management: Use Radix built-in focus trapping

Detailed Documentation

Resource Description
scripts/ Templates: CVA component, extended button, dialog, dropdown
checklists/ shadcn setup, accessibility audit checklists
references/ CVA system, OKLCH theming, cn() utility, focus management

Design System

Design token architecture, spacing, typography, and interactive component states.

Rule File Key Pattern
Token Architecture rules/design-system-tokens.md W3C tokens, OKLCH colors, Tailwind @theme
Spacing Scale rules/design-system-spacing.md 8px grid, Tailwind space-1 to space-12
Typography Scale rules/design-system-typography.md Font sizes, weights, line heights
Component States rules/design-system-states.md Hover, focus, active, disabled, loading, animation presets

Design System Components

Component architecture patterns with atomic design and accessibility.

Rule File Key Pattern
Component Architecture rules/design-system-components.md Atomic design, CVA variants, WCAG 2.1 AA, Storybook

Forms

React Hook Form v7 with Zod validation and React 19 Server Actions.

Rule File Key Pattern
React Hook Form rules/forms-react-hook-form.md useForm, field arrays, Controller, wizards, file uploads
Zod & Server Actions rules/forms-validation-zod.md Zod schemas, Server Actions, useActionState, async validation

Modern CSS & Tooling

Modern CSS patterns, Tailwind v4, and component documentation tooling for 2026.

Rule File Key Pattern
CSS Cascade Layers rules/css-cascade-layers.md @layer ordering, specificity-free overrides, third-party isolation
Tailwind v4 rules/tailwind-v4-patterns.md CSS-first @theme, native container queries, @max-* variants
Storybook Docs rules/storybook-component-docs.md CSF3 stories, play() interaction tests, Chromatic visual regression

UX Foundations

Cognitive-science-grounded UI/UX principles with specific numeric thresholds for production-quality interfaces.

Rule File Key Pattern
Visual Hierarchy rules/visual-hierarchy.md Button tiers, de-emphasis, F/Z scan, Von Restorff, proximity, max-width
Typography Thresholds rules/typography-thresholds.md 65ch line length, 1.4–1.6 line height, rem units, modular type scale
Color System rules/color-system.md OKLCH 9-shade scales, semantic categories, no true black, brand-tinted neutrals
Empty States rules/empty-states.md Skeleton-first, icon + headline + description + CTA, cause-specific tone

Related Skills

  • ork:accessibility - WCAG compliance and React Aria patterns
  • ork:testing-unit - Component testing patterns
how to use ui-components

How to use ui-components on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ui-components
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/yonatangross/orchestkit --skill ui-components

The skills CLI fetches ui-components from GitHub repository yonatangross/orchestkit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ui-components

Reload or restart Cursor to activate ui-components. Access the skill through slash commands (e.g., /ui-components) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.536 reviews
  • Pratham Ware· Dec 20, 2024

    Registry listing for ui-components matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Martinez· Dec 20, 2024

    ui-components is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aisha Shah· Dec 4, 2024

    Keeps context tight: ui-components is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chen Dixit· Nov 23, 2024

    Registry listing for ui-components matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Tariq Abebe· Nov 11, 2024

    ui-components reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Li Perez· Oct 14, 2024

    ui-components fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ava Flores· Oct 2, 2024

    I recommend ui-components for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Yash Thakker· Sep 13, 2024

    ui-components reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kaira Okafor· Sep 1, 2024

    ui-components is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Valentina Sanchez· Aug 20, 2024

    Useful defaults in ui-components — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 36

1 / 4