About magic-ui
A skill for developers and coding agents building React/Next.js interfaces with Magic UI components. It guides component selection, installation, integration, and quality checks.
Key features
- 01Maps UI needs to Magic UI components
- 02Guides shadcn registry installation
- 03Covers section-level implementation patterns
- 04Checks accessibility, responsiveness, and performance
Use cases
- 01Adding animated effects to a hero section
- 02Replacing custom animation with Magic UI components
- 03Troubleshooting @magicui imports or installation
MCP support
The README mentions optional MCP setup for AI IDE workflows, but does not describe specific MCP capabilities.
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ magicuidesign/ magicui --skill magic-uiAfter installing, type/magic-uiin Claude Code to confirm it loaded.
Bundled filesreferences/components.mdreferences/recipes.md
Details
From the project READMEMagic 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
- 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.
- Confirm project prerequisites.
- Project should be React/Next.js with Tailwind CSS.
- shadcn must be initialized before adding registry components:
npx shadcn@latest init
- Install the selected component(s).
npx shadcn@latest add @magicui/<component-slug>
Example:
npx shadcn@latest add @magicui/magic-card
- 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.
- 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
- Read
- For section-level implementation patterns:
- Read
references/recipes.md
- Read
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.jsonor registry init error:- Run
npx shadcn@latest initin the project root.
- Run
- 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
Comments
Markdown supported