shadcn-ui ui
COMMUNITYLABSCO SUMMARY
The larger one, named simply shadcn, is a general-purpose assistant for the whole ecosystem: adding components, searching and fixing existing ones, styling, composing chat interfaces, and working with component registries, presets, and a project's components.json file. The other, migrate-radix-to-base, does one narrow job — moving a shadcn project, a single component or a whole codebase, off Radix UI primitives and onto Base UI, shadcn's newer underlying library.
shadcn-ui/ui's own README says nothing about either skill — it describes the component library itself and points to the hosted docs, not to this material — so everything above comes from the two skills' own descriptions, not from any maintainer framing we could check it against. That's workable for two skills this specific, but it means we have no stated intent behind them beyond what each one claims for itself.
READ THE FULL ANALYSIS
Three more skills have existed in this repository and are no longer live. We have no material saying what they did or why they dropped out — the database records them as gone, and nothing in what we could read reconstructs a retired skill's history. If you need that history, the repository's own commits will have it; this page does not.
WHAT'S INSIDE
2 showing · 2 totalmigrate-radix-to-base
Swaps the library underneath a React project's interface components — out with Radix, in with Base UI — one component at a time, checking the project still builds after each one.
shadcn
Most of a screen can be assembled from shadcn/ui's ready-made parts rather than written by hand — this picks which part to use, installs it, and keeps the result styled the way the library expects.
HOW TO GET IT
npx skills add shadcn-ui/uinpx skills add shadcn-ui/ui --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.