What problem does it solve? When building shadcn/ui components, developers must know whether the project uses Radix UI or Base UI primitives, since their APIs differ significantly (asChild vs render, Overlay vs Backdrop, Content vs Popup). Mixing the two APIs in one component breaks the UI, and hand-writing component internals instead of using registry source leads to drift. ## Core Features & Use Cases - Primitive API Mapping: Provides a 1:1 mapping table between Radix UI and Base UI parts for Dialog, Select, Tooltip, Accordion, Popover, and Menu components. - Composition Pattern Guidance: Documents the asChild pattern for Radix and the render prop pattern for Base UI with working code snippets. - MCP-Driven Component Sourcing: Requires consulting the shadcn MCP registry (search, view, get add command) before adding any component, using registry source as truth. - Use Case: You need to add a Dialog to a project. The skill first detects the primitive via shadcn-detection, fetches the component source from the shadcn registry, then adapts it using the correct composition pattern and part names. ## Quick Start Ask the agent to add a shadcn Dialog component to the project, making sure it detects whether the project uses Radix UI or Base UI first.
