agentleFS
Sign inStart free
RoentekRoentek/Claude_Code_Boilerplate_Framework/.claude/skills/21st-magic/SKILL.md

21st-magic

Skill4 starsChanged 6 months agoMITView on GitHub

AI-powered UI component generation and inspiration via 21st.dev Magic MCP. MCP-first (no standalone CLI for component ops — @21st-dev/cli is setup-only). Requires TWENTYFIRST_DEV_API_KEY in .claude/settings.local.json. Use /21st-magic when asked to: - "Find a component for X" → 21st_magic_component_inspiration - "Build/generate a component for X" → 21st_magic_component_builder - "Improve this component" / "make it look like Y" → 21st_magic_component_refiner - "Get the logo for [Brand]" → logo_search Prefer monet-mcp for landing page section components (hero, pricing, testimonials). Prefer /extract-design when you…

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer /extract-design: when you need design tokens, not components.

    line 30
  2. Distinctive:

    Search the 21st.dev registry for existing components matching a description.

    line 37
  3. Distinctive:

    All component output is React + TypeScript by default.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/21st-magic — 21st.dev Magic UI Component Tools

AI-powered UI component generation and inspiration via 21st.dev Magic MCP.

MCP-first (no standalone CLI for component ops — @21st-dev/cli is setup-only). Requires TWENTYFIRST_DEV_API_KEY in .claude/settings.local.json.

Tools Available

ToolUse When
mcp__21st-dev-magic__21st_magic_component_inspirationBrowse/search existing components by description or style — free tier
mcp__21st-dev-magic__21st_magic_component_builderGenerate a new UI component from a prompt — Pro required
mcp__21st-dev-magic__21st_magic_component_refinerImprove or restyle an existing component — Pro required
mcp__21st-dev-magic__logo_searchFind SVG brand logos by company name — free tier

Routing

Use /21st-magic when asked to:

  • "Find a component for X" → 21st_magic_component_inspiration
  • "Build/generate a component for X" → 21st_magic_component_builder
  • "Improve this component" / "make it look like Y" → 21st_magic_component_refiner
  • "Get the logo for [Brand]" → logo_search

Prefer monet-mcp for landing page section components (hero, pricing, testimonials). Prefer /extract-design when you need design tokens, not components.

Usage

Component Inspiration (free)

Search the 21st.dev registry for existing components matching a description. Returns component previews, code snippets, and registry URLs.

Component Builder (Pro)

Generates a production-ready React/TypeScript component from a natural language prompt. Follows Tailwind CSS + shadcn/ui conventions by default.

Component Refiner (Pro)

Takes existing component code + a refinement instruction. Returns improved code preserving the component's structure.

Logo Search (free)

Returns SVG markup for brand logos. Use for nav bars, partner sections, tech stacks.

Setup

Two separate keys — both go in .claude/settings.local.json → env block:

"TWENTYFIRST_DEV_MAGIC_API_KEY": "your-magic-key",
"TWENTYFIRST_DEV_CLI_API_KEY":   "your-cli-key"
KeySourceUsed by
TWENTYFIRST_DEV_MAGIC_API_KEYhttps://21st.dev/magic/console → API Keys21st-dev-magic MCP (component gen/search)
TWENTYFIRST_DEV_CLI_API_KEYhttps://21st.dev/studio → Settings → API Keys@21st-dev/cli (publish to registry)

Restart Claude Code after adding keys — MCP activates automatically. Free tier (Magic key): Inspiration + Logo Search. Pro ($20/mo): Builder + Refiner.

Notes

  • @21st-dev/cli with TWENTYFIRST_DEV_CLI_API_KEY — studio operations (publish, manage components in the 21st.dev registry). Not needed for component generation.
  • 21st-dev-magic MCP with TWENTYFIRST_DEV_MAGIC_API_KEY — all component generation/search in Claude Code.
  • All component output is React + TypeScript by default.
  • Components reference @/components/ui/ (shadcn/ui) path aliases — adjust for your project.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free