shadcn-add

Add or update shadcn/ui components in a Next.js project via the official CLI.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/manhthien2005/FixNow --skill shadcn-add-manhthien2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn-add
Source: https://github.com/manhthien2005/FixNow/tree/main/.claude/skills/shadcn-add
Command: npx skills add https://github.com/manhthien2005/FixNow --skill shadcn-add-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you add or update shadcn/ui primitives in a FixNow Next.js project without manually copying component source, reducing setup errors and keeping the UI aligned with the official registry.

Core Features & Use Cases

  • Initialize shadcn: Set up the project with the expected shadcn configuration when components.json is missing.
  • Add or update primitives: Install needed components such as button, input, select, table, dialog, and sheet through the official CLI.
  • Protect generated code: Avoid hand-editing components/ui/*; extend behavior in feature components instead.
  • Use case: When a page needs a missing UI primitive, this Skill guides the exact shadcn CLI workflow to add it safely and consistently.

Quick Start

Ask to add the missing shadcn component for the current FixNow page using the official CLI workflow.

Frequently Asked Questions about shadcn-add

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

FAQPage Schema
How do I add shadcn UI components to a Next.js project?

To add shadcn UI components to a Next.js project, use the official CLI to install primitives like buttons, forms, and tables directly from the registry, ensuring safe handling without manual source copying.

Do I need to initialize shadcn before adding UI components?

Yes, you need to initialize shadcn to set up the expected configuration if the components.json file is missing before you can safely add or update UI primitives using the CLI.

Can I manually edit shadcn UI components generated in my project?

You should avoid hand-editing generated shadcn UI components in the components/ui directory; instead, extend their behavior within your feature components to maintain alignment with the official registry.

What is the best way to update existing shadcn primitives in Next.js?

The best way to update existing shadcn primitives in Next.js is by running the official shadcn CLI workflow, which safely applies updates to UI components like dialogs and sheets without requiring manual source code modifications.

Why does my shadcn setup fail when adding UI components to Next.js?

Your shadcn setup may fail if the project is not properly initialized with a components.json file, or if dependencies are missing, preventing the CLI from safely installing the required UI primitives.