fusengine/shadcn-registries
plugins/shadcn-expert/skills/shadcn-registries/SKILL.md
Configure shadcn/ui registries, components.json, and CLI commands. Covers default Radix registry, Base UI registry, and custom registries. Use when: configuring shadcn/ui registries, components.json, or CLI add/init commands.
$ install --global
skillsauthnpx skillsauth add fusengine/agents shadcn-registriesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 16, 2026, 2:53 AM180.5s3 files scanned
SKILL.md
- name:
- shadcn-registries
- description:
- Configure shadcn/ui registries, components.json, and CLI commands. Covers default Radix registry, Base UI registry, and custom registries. Use when: configuring shadcn/ui registries, components.json, or CLI add/init commands.
- shadcn-ui:
- 2.x
- shadcn-cli:
- latest
- user-invocable:
- true
- allowed-tools:
- Read, Write, Edit, Bash, Glob, Grep, mcp__shadcn__search_items_in_registries, mcp__shadcn__view_items_in_registries, mcp__shadcn__get_add_command_for_items
- references:
- references/registry-config.md, references/templates/registry-setup.md
- related-skills:
- shadcn-components, shadcn-detection
shadcn Registries
Agent Workflow (MANDATORY)
Before registry configuration, use TeamCreate:
- fuse-ai-pilot:explore-codebase - Find existing components.json
- fuse-ai-pilot:research-expert - Verify latest CLI options via Context7
After: Run fuse-ai-pilot:sniper for validation.
Overview
| Registry | Primitives | Style |
|----------|-----------|-------|
| @shadcn (default) | Radix UI | new-york, default |
| @basecn | Base UI | base-vega |
| Custom | Any | Custom |
Critical Rules
- ALWAYS detect PM before any CLI command (use {runner})
- ALWAYS consult MCP before adding components
- NEVER mix registries in same project
- KEEP components.json in sync with actual primitive
- USE CLI for adding components, never manual copy
Architecture
project/
├── components.json # shadcn/ui configuration
├── components/ui/ # Generated components
└── lib/utils.ts # Utility functions (cn)
-> See registry-setup.md for complete setup
CLI Commands
ALWAYS use detected package manager (run shadcn-detection first).
{runner} = bunx | npx | pnpm dlx | yarn dlx
# Initialize
{runner} shadcn@latest init
{runner} shadcn@latest init --style new-york
# Add components (default registry = Radix)
{runner} shadcn@latest add button dialog select
# Add from Base UI registry
{runner} shadcn@latest add --registry=basecn button dialog
MCP (MANDATORY)
mcp__shadcn__search_items_in_registries -> find component
mcp__shadcn__get_add_command_for_items -> get exact CLI command
components.json Structure
{
"$schema": "https://ui.shadcn.com/schema.json",
"style": "new-york",
"tailwind": { "config": "tailwind.config.ts", "css": "app/globals.css" },
"aliases": { "components": "@/components", "utils": "@/lib/utils" }
}
-> See registry-config.md for full schema
Reference Guide
Concepts
| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Registry Config | registry-config.md | Setting up components.json |
Templates
| Template | When to Use | |----------|-------------| | registry-setup.md | Initial project setup |
Best Practices
DO
- Use MCP to check registry before adding
- Keep components.json in sync with actual primitive
- Use CLI for adding, not manual copy
DON'T
- Mix registries in same project
- Edit component internals without checking registry source
- Skip components.json configuration
Related Skills
fusengine/ux-copy
testing
VerifiedTrustedCommunity
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-webapp
development
VerifiedTrustedCommunity
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-web
development
VerifiedTrustedCommunity
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-system
development
VerifiedTrustedCommunity
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.
20SKILL.mdUpdated Jul 13, 2026