shadcn

Manage shadcn/ui components, registries, and presets in Next.js projects.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Mohamedghaly140/sg-shop-web --skill shadcn-mohamedghaly140
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/Mohamedghaly140/sg-shop-web/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/Mohamedghaly140/sg-shop-web --skill shadcn-mohamedghaly140

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Core Features & Use Cases

  • Centralizes management of shadcn/ui components, registries, and presets to keep projects consistent
  • Provides project context, component docs, and usage examples to accelerate development
  • Supports key workflows like init, apply, add, docs, and info across multi-repo setups

Quick Start

Initialize or adjust a shadcn/ui project and apply presets to start building consistent components.

Frequently Asked Questions about shadcn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage shadcn/ui components and presets across multiple Next.js repositories?

To manage shadcn/ui components across repositories, you centralize init, add, and apply workflows using a components.json file. This ensures consistent component composition, semantic token usage, and CLI-guided best-practice checks across all project setups.

What is the best way to organize a shadcn/ui component registry in a Next.js project?

The best way to organize a shadcn/ui component registry is to define CLI-guided workflows and coding standards for component composition. Utilizing a components.json file ensures semantic token usage and consistency across your Next.js project and presets.

How do I apply a custom preset to an existing shadcn/ui project?

To apply a custom preset to an existing shadcn/ui project, you use the apply workflow triggered via the CLI. This adjusts your current setup by switching configurations and enforcing coding standards defined within the components.json file.

Does shadcn/ui work with component registries for multi-repo setups?

Yes, shadcn/ui works with component registries for multi-repo setups by supporting centralized workflows like init, add, and info. This keeps component documentation, usage examples, and styling consistent across different repositories.

Why does my shadcn/ui component styling break when switching presets?

Shadcn/ui component styling may break when switching presets if semantic token usage and coding standards for component composition are not properly aligned. Enforcing CLI-guided best-practice checks ensures consistency across the applied configurations.