shadcn-ui-builder

Add or update shadcn/ui components across a monorepo using the shadcn CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ldsgroups225/Yeko --skill shadcn-ui-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn-ui-builder
Source: https://github.com/ldsgroups225/Yeko/tree/main/.github/skills/shadcn-ui-builder
Command: npx skills add https://github.com/ldsgroups225/Yeko --skill shadcn-ui-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines adding or updating shadcn/ui components across a large monorepo, ensuring consistency with Tailwind v4, a shared UI package, and CSS variable theming.

Core Features & Use Cases

  • Add new components or blocks via the shadcn CLI, resolving monorepo paths correctly.
  • Update existing components to adhere to repo conventions (semantic tokens, kebab-case filenames, and shared UI patterns).
  • Inspect registry items and manage component placement across shared packages and app-specific composition.

Quick Start

From the repo root, run the shadcn CLI to add or update a component and let it resolve paths within the monorepo.

Frequently Asked Questions about shadcn-ui-builder

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

FAQPage Schema
How do I add shadcn/ui components to a monorepo using the CLI?

Run the shadcn CLI from the repo root to add shadcn/ui components across a monorepo, ensuring correct path resolution to shared UI packages, kebab-case naming, and semantic token application.

Does shadcn CLI work with Tailwind v4 and shared UI packages?

The shadcn CLI supports Tailwind v4 by enforcing CSS variable theming and semantic tokens, ensuring components integrate correctly within a shared UI package across a monorepo.

What is the best way to update existing shadcn/ui components across multiple apps?

Update existing shadcn/ui components across apps by running the shadcn CLI to safely apply shared UI blocks, enforcing repo-wide conventions like semantic tokens and kebab-case filenames.

How do I inspect shadcn registry items for a monorepo?

Use the shadcn CLI to inspect registry items, verifying component metadata and managing placement across shared packages and app-specific compositions within a monorepo.

Why does my shadcn component placement fail in a monorepo?

Component placement fails when files are not correctly placed under shared UI paths, violating repo conventions like kebab-case naming and semantic token usage enforced by the shadcn CLI.

Do I need a shared UI package to use shadcn in a monorepo?

Using a shared UI package ensures proper path resolution and enforces consistent component guidelines, semantic tokens, and correct placement across apps and packages in a monorepo.