Manage shadcn/ui components, presets, and project context via CLI workflows.
npx skills add https://github.com/znarfm/vet --skill shadcn-znarfm
Please help me install this Agent Skill. Skill: shadcn Source: https://github.com/znarfm/vet/tree/main/.agents/skills/shadcn Command: npx skills add https://github.com/znarfm/vet --skill shadcn-znarfm
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".
Initialize a project with a shadcn preset and manage components using the CLI.
High-intent search queries and answers about installing and using this skill.
To manage shadcn/ui components, use the CLI to initialize projects, add components, resolve documentation, and switch presets. This provides project context and usage examples directly from component registries for consistent UI tooling.
Switching shadcn/ui presets is handled by applying a --preset code during project creation or using CLI commands. This streamlines workflow transitions and ensures consistent component usage across teams working within the same components.json configuration.
Yes, it applies to any project utilizing component registries, presets, or a components.json file. It centralizes management by resolving documentation and providing usage examples from those registries for your custom UI components.
A components.json file is needed when managing shadcn/ui components, applying presets, or resolving documentation. It provides the necessary project context for the CLI to accurately add, search, and style UI components across your codebase.
Documentation resolution issues often stem from missing project context or an invalid components.json setup. The CLI relies on this configuration to fetch accurate component docs and usage examples from the specified registries.
Yes, you can debug, fix, and style shadcn/ui components using the CLI. It centralizes these tasks by leveraging project context and registry documentation to ensure consistent component composition and styling.
BuilderIOConfigure shadcn/ui components and validate imports using components.json.
snake-dev-teamStyle React interfaces with shadcn/ui components and Tailwind CSS.
pavan53732Transform UI style requirements into React and TypeScript code with Tailwind CSS.
LiangNiangSearch, view, and import UI components from multiple registries.
