What problem does it solve?
It prevents teams from shipping shadcn/ui integrations that break Radix accessibility behaviors, lose keyboard support, or regress performance due to poor composition and styling patterns.
Core Features & Use Cases
- Accessible Radix-first implementations: preserve ARIA attributes, focus management, and keyboard navigation when composing dialogs, triggers, and primitives.
- Robust component architecture: enforce ref forwarding, class composition via cn(), and safe variant patterns with CVA to avoid style bleeding and runtime issues.
- Production-grade UI patterns: apply shadcn/ui theming with CSS variables (including dark mode), implement form correctness with React Hook Form + Zod, and handle data rendering with TanStack Table/Virtual for large datasets.
- Use Cases: code review and refactoring for UI libraries, building forms and tables in Next.js, and creating maintainable component APIs that support scalable design systems.
Quick Start
Use the shadcn skill to review and refactor your shadcn/ui component code for accessibility, styling consistency, and performance, then apply the highest-impact rule fixes from the generated guidance.