shadcn-vue

noartem/laravel-vue-skills · updated May 25, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/noartem/laravel-vue-skills --skill shadcn-vue
0 commentsdiscussion
summary

Accessible Vue/Nuxt component library with Reka UI, Tailwind CSS, and dark mode support.

  • Provides 50+ pre-built, accessible components (buttons, cards, dialogs, data tables, forms) installable via CLI with automatic TypeScript path configuration
  • Requires initialization with npx shadcn-vue@latest init to set up components.json , Tailwind CSS variables, and path aliases before adding components
  • Supports dark mode through CSS variables, Auto Form for dynamic form generation, and TanStac
skill.md

shadcn-vue


Quick Start (3 Minutes)

For Vue Projects (Vite)

1. Initialize shadcn-vue

npx shadcn-vue@latest init

During initialization:

  • Style: New York or Default (cannot change later!)
  • Base color: Slate (recommended)
  • CSS variables: Yes (required for dark mode)

2. Configure TypeScript Path Aliases

// tsconfig.json
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

3. Configure Vite

// vite.config.ts
import { defineConfig } from "vite";
import vue from "@vitejs/plugin-vue";
import tailwindcss from "@tailwindcss/vite"; // Tailwind v4
import path from "path";

export default defineConfig({
  plugins: [vue(), tailwindcss()],
  resolve: {
    alias: {
      "@": path.resolve(__dirname, "./src"),
    },
  },
});

4. Add Your First Component

npx shadcn-vue@latest add button

Quick Reference

Need Command or file
Initialize project npx shadcn-vue@latest init
Add component npx shadcn-vue@latest add button
Add multiple components npx shadcn-vue@latest add button card dialog
Build registry JSON npx shadcn-vue@latest build
Generate component docs npx tsx scripts/generate-shadcn-components.ts
Enable CSS variables components.jsontailwind.cssVariables: true
Add registry namespace components.jsonregistries map
Opencode MCP init npx shadcn-vue@latest mcp init --client opencode
Codex MCP config ~/.codex/config.toml with mcp_servers.shadcn

Bundled Resources

Templates (templates/):

  • quick-setup.ts - Complete setup guide for Vue/Nuxt with examples (190 lines)

References (references/):

  • cli.md - CLI commands and options
  • mcp.md - MCP setup, client configs, prompts
  • theming.md - Theming and cssVariables
  • error-catalog.md - All 7 documented issues with solutions (267 lines)
  • component-examples.md - All 50+ component examples with code
  • dark-mode-setup.md - Complete dark mode implementation guide
  • data-tables.md - Data tables with TanStack Table

Component Documentation (components/):

  • references/components.md - Index of all shadcn-vue components
  • components/<component>.md - Individual component documentation with installation, usage, and examples

Official Documentation:


When to Load References

Load these references based on the task:

  1. Load references/error-catalog.md when:

    • User encounters "component not found" or import errors
    • Setup commands fail or configuration issues arise
    • Tailwind CSS variables or TypeScript paths broken
    • Trigger phrases: "not working", "error", "fails to", "broken"
  2. Load references/components.md when:

    • User asks what components are available (names, categories, status)
    • User needs to add/use a component and wants the correct install/import paths
    • You need to confirm a component exists before recommending a custom build
  3. Load references/component-examples.md when:

    • User asks "how do I implement [component]?"
    • Need copy-paste examples for specific components
    • Building forms, tables, navigation, or data display
    • Trigger phrases: "example", "how to use", "implement", "code sample"
  4. Load references/cli.md when:

    • User asks how to run the CLI (init, add, update) or what prompts mean
    • Need the exact command/flags for installing one or more components
    • Troubleshooting CLI-related issues (registry, paths, overwrites)
  5. Load references/dark-mode-setup.md when:

    • Implementing dark mode / theme switching
    • User mentions Vue 3 + Vite, Nuxt, or Astro setup
    • Need composable patterns for theme management
    • Trigger phrases: "dark mode", "theme", "light/dark", "color scheme"
  6. Load references/theming.md when:

    • User wants to customize theme tokens via CSS variables (cssVariables, :root, .dark)
    • Need to wire Tailwind to CSS-variable-based colors and radii
    • Setting up/adjusting design tokens (colors, radius, typography) for shadcn-vue
  7. Load references/mcp.md when:

    • Setting up MCP server for opencode, Codex, Cursor, VS Code
    • Configuring registries in components.json
    • Troubleshooting missing components or registry namespaces
    • Trigger phrases: "MCP", "opencode", "codex", "cursor", "registry"
  8. Load references/data-tables.md when:

    • Building sortable/filterable/paginated tables
    • User mentions TanStack Table or DataTable
    • Trigger phrases: "data table", "table", "tanstack", "sorting", "pagination"

Critical Rules

Always Do

Run init before adding components

  • Creates required configuration and utilities
  • Sets up path aliases

Use CSS variables for theming (cssVariables: true)

  • Enables dark mode support
  • Flexible theme customization

Configure TypeScript path aliases

  • Required for component imports
  • Must match components.json aliases

Keep components.json in version control

  • Team members need same configuration
  • Documents project setup

Never Do

Don't change style after initialization

  • Requires complete reinstall
  • Reinitialize in new directory instead

Don't mix Radix Vue and Reka UI v2

  • Incompatible component APIs
  • Use one or the other

Don't skip TypeScript configuration

  • Component imports will fail
  • IDE autocomplete won't work

Don't use without Tailwind CSS

  • Components are styled with Tailwind
  • Won't render correctly

Common Mistakes

  • Running add before init and missing components.json.
  • Forgetting to enable the MCP server in the client UI/config.
  • Mis-typed registry namespaces (@namespace/component).
  • Using CSS variable classes without tailwind.cssVariables: true.

CLI Commands Reference

init Command

# Initialize in current directory
npx shadcn-vue@latest init

# Initialize in specific directory (monorepo)
npx shadcn-vue@latest init -c ./apps/web

add Command

# Add single component
npx shadcn-vue@latest add button

# Add multiple components
npx shadcn-vue@latest add button card dialog

# Add all components
npx shadcn-vue@latest add --all

diff Command

# Check for component updates
npx shadcn-vue@latest diff button

mcp Command

# Initialize MCP for specific client
npx shadcn-vue@latest mcp init --client opencode
npx shadcn-vue@latest mcp init --client codex
npx shadcn-vue@latest mcp init --client cursor
npx shadcn-vue@latest mcp init --client vscode

Configuration

shadcn-vue uses components.json to configure:

  • Component paths (@/components/ui)
  • Utils location (@/lib/utils)
  • Tailwind config paths
  • TypeScript paths

Full example: See templates/components.json or generate via npx shadcn-vue@latest init


Utils Library

The @/lib/utils.ts file provides the cn() helper for merging Tailwind classes:

  • Combines multiple className strings
  • Uses clsx + tailwind-merge for conflict resolution

Auto-generated by shadcn-vue init - no manual setup needed.

how to use shadcn-vue

How to use shadcn-vue on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add shadcn-vue
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/noartem/laravel-vue-skills --skill shadcn-vue

The skills CLI fetches shadcn-vue from GitHub repository noartem/laravel-vue-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/shadcn-vue

Reload or restart Cursor to activate shadcn-vue. Access the skill through slash commands (e.g., /shadcn-vue) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.637 reviews
  • Shikha Mishra· Dec 20, 2024

    I recommend shadcn-vue for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Kapoor· Dec 20, 2024

    shadcn-vue fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mateo Brown· Dec 12, 2024

    Useful defaults in shadcn-vue — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Kim· Dec 8, 2024

    Registry listing for shadcn-vue matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Hana Park· Nov 27, 2024

    Solid pick for teams standardizing on skills: shadcn-vue is focused, and the summary matches what you get after install.

  • Xiao Torres· Nov 23, 2024

    shadcn-vue reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mateo Taylor· Nov 11, 2024

    We added shadcn-vue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Patel· Nov 3, 2024

    shadcn-vue has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sofia Shah· Oct 22, 2024

    Keeps context tight: shadcn-vue is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Maya Mensah· Oct 18, 2024

    We added shadcn-vue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 37

1 / 4