Shadcn Component Discovery

shadcn Component Discovery

Surface existing components from across the shadcn ecosystem — including registries the user hasn't configured yet — before spending effort on custom implementations.

How This Complements the Official shadcn Skill

The official shadcn skill (shipped with CLI v4) searches the registries declared in the user's components.json. That's the right tool once the user has decided which registries to use.

This skill fills the upstream gap: ecosystem-wide awareness. It helps the user find and choose registries they may not yet have configured — Magic UI for animations, Aceternity for hero sections, AI Elements for chat interfaces, ElevenLabs UI for voice components, and so on. Use this skill for "what exists out there"; let the official skill handle "install this thing I know about."

When both skills apply, this one runs first (discovery), then the official skill takes over for installation and project-aware work.

Core Principle

Search before building. Most UI needs have been solved in the shadcn ecosystem. The cost of a 10-second registry check is almost always less than custom-building something that already exists.

When to Trigger

Proactive triggers (activate before writing any component code):

• User asks to build a table, form, modal, sidebar, dashboard, auth page, landing section, animation, carousel, chart, or any standard UI pattern
• User describes a feature that implies UI (e.g. "add user accounts management" → table; "let users pick a date range" → date picker)
• User mentions building something "like X" where X is a common pattern

Explicit triggers (user directly requests search):

• "Find a component for..."
• "Is there a shadcn component for..."
• "Search registries for..."
• "What exists for..."
• "Any good [category] components?"
• Direct mentions of specific registries (@animate-ui, Magic UI, Aceternity, Tailark, etc.)

Workflow

Step 1: Clarify the Need

Before searching, confirm:

• Functionality: What must it do? (e.g. sortable + filterable + paginated table)
• Style: Animated, minimal, accessible-first, dense, brutalist?
• Constraints: Must support keyboard nav? Drag-drop? Mobile-first? SSR?

A two-sentence clarification beats five searches with the wrong query.

Step 2: Search

Three paths depending on tool availability. The official shadcn MCP is strongly preferred when the user has a shadcn project — it returns real results with code examples.

Path A: Official shadcn MCP (preferred)

If the shadcn MCP server is running (configured via npx shadcn@latest mcp init or equivalent), use its tools directly:

1. mcp__shadcn__search_items_in_registries
   - registries: ["@shadcn", "@blocks", "@animate-ui", "@reui", "@diceui"]
   - query: "<search term>"
   - limit: 10

2. For promising results, get full details:
   mcp__shadcn__view_items_in_registries
   - items: ["@registry/component-name", "@registry/other"]

3. For implementation examples:
   mcp__shadcn__get_item_examples_from_registries
   - query: "<component>-demo"

4. For the install command:
   mcp__shadcn__get_add_command_for_items
   - items: ["@registry/chosen-component"]

The MCP only searches registries configured in the user's components.json. If the user is looking for something specialized, suggest adding a relevant registry to components.json first — see references/registries.md for recommendations and configuration snippets.

Path B: shadcn CLI (no MCP, but shadcn project)

If there's a components.json but no MCP is configured, use the CLI commands that shipped with CLI v3:

# Search across configured registries
npx shadcn@latest search "<term>"

# Preview a component before installing
npx shadcn@latest view @registry/component-name

# List everything available in a registry
npx shadcn@latest list @registry

Suggest adding the MCP for better agent integration: npx shadcn@latest mcp init.

Path C: No project context

If there's no shadcn project yet, or the user is just exploring:

• Recommend registries from references/registries.md based on their described need
• Link directly to the registry's website so they can browse
• Offer to help set up a shadcn project (npx shadcn@latest init) once they've picked direction

Step 3: Present Findings

Match the response format to the context. Keep it scannable — the user is about to make a decision, not read an essay.

Proactive check (during build flow)

When the user didn't explicitly ask to search but you searched anyway:

Before building custom, I found existing options:

1. **@registry/component-name** — [one-line description]
2. **@registry/alternative** — [one-line description]

Want me to install one, or build custom?

Keep it under five lines. The user is in flow; don't derail them.

Explicit search (user asked)

## Results for "<query>"

**Top matches:**

### @registry/component-name ⭐
[What it does in one sentence]
- Fits because: [specific to their need]
- Install: `npx shadcn@latest add @registry/component-name`

### @registry/alternative
[What it does in one sentence]
- Fits because: [specific to their need]
- Install: `npx shadcn@latest add @registry/alternative`

---
Install [1] or [2], see more results, view code example, or build custom?

Comparison (multiple good options, choice matters)

Use a short table when 3+ options are genuinely viable and trade off differently. Follow with a recommendation and the install command for the recommended one. Don't table-ify everything — it's heavier than plain prose and should earn its place.

Step 4: Execute the Choice

• Install chosen: Run the add command, then customize via props / composition as needed
• See more: Return additional matches, continue pagination
• View code: Fetch example via get_item_examples_from_registries or the registry's demo URL
• Build custom: Proceed — but reference the closest existing component for composition patterns (CVA, cn(), data-slot, semantic tokens)

Search Strategy

Effective Query Terms

Short, concrete nouns work best. Keep queries to 1–3 words.

Registry Specialties (Quick Pick)

For the full catalog including URLs, configuration snippets, and registry specialties, see references/registries.md.

Response Requirements

Every discovery response should surface:

1. What was searched — the query used
2. Top 2–3 recommendations — registry-qualified name, one-line description, why it fits
3. Install command — ready to copy
4. A recommendation — which to pick, when there's a clear fit
5. Next-step options — install, view code, see more, build custom

Skip anything beyond this unless the user asks. Brevity respects flow.

Examples

Proactive check