Install one or more Cult UI components into the current project with the shadcn CLI, after reading their docs, then adapt them to the project.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Install these Cult UI components into the current project: $ARGUMENTS
Follow the cult-ui skill's rules throughout. The catalog is at ${CLAUDE_PLUGIN_ROOT}/skills/cult-ui/references/components.md (Glob **/skills/cult-ui/references/components.md if the path does not resolve). The setup guide is the references/setup.md file beside it.
For each requested component, Grep the catalog case-insensitively for its name or slug and take the install name (the install @cult-ui/<name> field).
animated-* name is requested, install the matching halo-* component instead and say so; the animated-* items are deprecated aliases.https://www.cult-ui.com/llms.txt and https://www.cult-ui.com/r/registry.json for a newer component. If it is still missing, stop and report it, and suggest /cult-ui:find.$ARGUMENTS is empty, ask which component to add.components.json exists at the project root. If it is missing, stop and ask before running npx shadcn@latest init, because init rewrites config and global CSS.components.json for the ui alias, so the output path is known.bun.lock/bun.lockb → bunx, pnpm-lock.yaml → pnpm dlx, yarn.lock → yarn dlx, otherwise npx.Fetch https://www.cult-ui.com/docs/components/<docs-slug>.md for each component (WebFetch; curl -sL for raw text). Note the required provider wrappers, props, variants, the demo usage, and any Next.js-only imports.
<runner> shadcn@latest add @cult-ui/<install-name> [@cult-ui/<another>]--overwrite unless the user asked for it. If the file already exists, show the diff and ask.shadcn@latest add https://www.cult-ui.com/r/<install-name>.json.references/setup.md.Read each file the CLI wrote, then:
next/image/next/link imports and swap next-themes usage for the project's theme source. In Astro, hydrate the component as a React island with a client:* directive.e5799dd
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.