magic-ui — Claude Code skill: what it does, how to install
The magic-ui skill teaches Claude Code to work with Magic UI components in React and Next.js: select animations, install via shadcn registry, and check accessibility.
npx skills add magicuidesign/magicui --skill magic-ui -a claude-codeWhat magic-ui does
The skill covers the full path from component selection to integration. The agent first clarifies the task (section type, motion intensity, responsive behavior), then checks for Tailwind CSS and shadcn initialization (npx shadcn@latest init), installs the component with npx shadcn@latest add @magicui/<slug>, and imports it from @/components/ui/. Built-in heuristics: marquee and avatar-circles for logo rails, globe and warp-background for hero sections, shiny-button for CTAs, grid-pattern for backgrounds.
Requires React or Next.js with Tailwind CSS and initialized shadcn. Without shadcn, registry components won't install. Post-install checks include semantic HTML, keyboard access, mobile layout, and avoiding heavy animation stacks.
The skill recommends starting with one core component plus one supporting effect, not stacking multiple high-motion effects in a single viewport. If the @/ alias isn't configured, the agent switches to relative imports.
What it helps with
- add a Magic UI component (marquee, globe, blur-fade, shiny-button)
- build a section with Magic UI effects (hero, testimonials, CTA, feature grid)
- replace custom animation code with a Magic UI component
- fix import or installation errors for
@magicui/* - validate accessibility and responsiveness of Magic UI sections
Example prompts for the agent
- add the magic-card component from Magic UI
- build a hero section with globe and blur-fade
- replace this animation code with shiny-button from Magic UI
How to install magic-ui
1Skills CLI (Vercel)
npx skills add magicuidesign/magicui --skill magic-ui -a claude-code2Manually: put the files in place
~/.claude/skills/magic-ui/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/magic-ui/
1Skills CLI (Vercel)
npx skills add magicuidesign/magicui --skill magic-ui -a codex2Manually: put the files in place
.agents/skills/magic-ui/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add magicuidesign/magicui --skill magic-ui -a cursor2Manually: put the files in place
.cursor/skills/magic-ui/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install magicuidesign/magicui magic-ui2Manually: put the files in place
.github/skills/magic-ui/SKILL.md1Skills CLI (Vercel)
npx skills add magicuidesign/magicui --skill magic-ui -a gemini-cli2Platform CLI
gemini skills install https://github.com/magicuidesign/magicui --path skills/magic-uiManually: put the files in place
.devin/skills/magic-ui/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add magicuidesign/magicui --skill magic-ui -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Similar
Questions about magic-ui
How to install magic-ui in Claude Code?
Run npx skills add magicuidesign/magicui --skill magic-ui -a claude-code. The skill will appear in ~/.claude/skills/magic-ui/SKILL.md.
What does the magic-ui skill do?
Teaches the agent to select, install, and integrate Magic UI components in React and Next.js via the shadcn registry. Includes accessibility and responsiveness checks.
What does magic-ui require to work?
A React or Next.js project with Tailwind CSS and initialized shadcn. Without shadcn, registry components cannot be installed.
Source text
SKILL.md · MIT
--- name: magic-ui description: Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (`@magicui/*`), integration patterns, and practical quality checks for accessibility and maintainability. metadata: short-description: Build and customize UIs with Magic UI components --- # Magic UI Use this skill when the task involves Magic UI components, animated UI sections, or converting static sections into interactive UI using the Magic UI registry. ## When To Apply Apply this skill when users ask to: - Add a Magic UI component (for example: marquee, globe, blur-fade, shiny-button) - Build a section with Magic UI effects (hero, testimonials, CTA, feature grid) - Replace custom animation code with Magic UI components - Troubleshoot installation/import issues for `@magicui/*` ## Core Workflow 1. Define the UI outcome first. - Identify section type, tone, motion intensity, and responsive behavior. - Keep motion intentional; avoid stacking many high-motion effects in one viewport. 2. Confirm project prerequisites. - Project should be React/Next.js with Tailwind CSS. - shadcn must be initialized before adding registry components: ```bash npx shadcn@latest init ``` 3. Install the selected component(s). ```bash npx shadcn@latest add @magicui/<component-slug> ``` Example: ```bash npx shadcn@latest add @magicui/magic-card ``` 4. Integrate into the target section. - Import from the generated path (typically `@/components/ui/<component-slug>`). - Keep component APIs intact; prefer prop/className customization over rewriting internals. - If docs mention extra dependencies or CSS keyframes, add them during integration. 5. Validate quality before finishing. - Accessibility: semantic HTML, keyboard access, meaningful labels/text. - Responsiveness: check mobile layout and overflow behavior. - Performance: avoid unnecessary client-only wrappers and heavy animation stacking. - Maintainability: keep new code modular and consistent with existing project conventions. ## References To Load On Demand - For component choice, install shape, and dependency expectations: - Read `references/components.md` - For section-level implementation patterns: - Read `references/recipes.md` ## Quick Component Selection Heuristics - Social proof/logo rails: `marquee`, `avatar-circles` - Hero visual impact: `globe`, `warp-background`, `animated-grid-pattern` - Text animation: `blur-fade`, `text-animate`, `word-rotate`, `sparkles-text` - CTA emphasis: `shiny-button`, `shimmer-button`, `rainbow-button` - Ambient backgrounds: `grid-pattern`, `dot-pattern`, `particles`, `flickering-grid` Start with 1 core component + 1 supporting effect, then expand only if needed. ## Troubleshooting - `components.json` or registry init error: - Run `npx shadcn@latest init` in the project root. - Import path mismatch (`@/` alias not configured): - Use the project's alias style or relative imports. - Visual mismatch after install: - Check for required global CSS/keyframes listed in the component docs. - Missing package errors: - Install dependencies listed in the component's manual installation steps. ## Reference Links - Magic UI docs: `https://magicui.design/docs` - Component docs: `https://magicui.design/docs/components` - Installation: `https://magicui.design/docs/installation` - MCP setup (optional, for AI IDE workflows): `https://magicui.design/docs/mcp`
© magicuidesign · MIT · magicuidesign/magicui