What problem does it solve?
shadcn_ui prevents UI drift and broken Radix/RHF integration by standardizing how your agents add and modify shadcn/ui components in the /opt/OS/saas codebase.
Core Features & Use Cases
- Scaffold and vendor shadcn components into each EOS SaaS repo so teams edit source code instead of relying on runtime packages.
- Use the correct composition patterns for Radix + triggers (including asChild to avoid nested interactive elements and accessibility bugs).
- Integrate forms and tables safely using the shadcn Form primitives (React Hook Form + zodResolver) and the DataTable pattern (TanStack Table).
Quick Start
Use this skill to add a new UI component set by asking: “Initialize shadcn for my EOS Vite app with the new-york style, then add the button, dialog, and form primitives in /opt/OS/saas/my-app so the components are vendored and ready to use.”