shadcn-core-registry

What problem does it solve?

This Skill prevents failed or inconsistent shadcn UI installs caused by incorrect components.json registry configuration, especially around immutable fields, namespace URL templates, alias mapping, env-var expansion, and Tailwind v3 vs v4 token shapes.

Core Features & Use Cases

• components.json registry correctness: Covers every key in components.json that affects registry resolution and installation behavior, including constraints, defaults, and immutability after init.
• URL template & namespace resolution: Explains the required {name} placeholder (and optional {style}), how the CLI materializes templates, and how it validates registry item JSON.
• Secure, production-ready custom registries: Guides safe header/params configuration using ${ENV_VAR} expansion to avoid committed secrets, and details registry.json hosting and item type schemas for publishers.

Quick Start

In a custom or private components.json, define the registries entry using a URL template that includes {name}, use ${ENV_VAR} for any secrets in headers, and keep style, tailwind.baseColor, and tailwind.cssVariables aligned before running init and add.