shadcn

Manage shadcn/ui components and project context via components.json workflows.

Updated Oct 8, 2024
One-click install
npx skills add https://github.com/connorfurby/my-portfolio --skill shadcn-connorfurby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/connorfurby/my-portfolio/tree/main/my-app/.agents/skills/shadcn
Command: npx skills add https://github.com/connorfurby/my-portfolio --skill shadcn-connorfurby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage shadcn/ui components and project context across a codebase, coordinating component creation, search, fixes, debugging, styling, and composition workflow.

Core Features & Use Cases

  • Adds, searches, fixes, and documents shadcn/ui components across projects that use a components.json registry.
  • Provides project context, component docs, and usage examples to accelerate UI development.
  • Triggers for common workflows like shadcn init, init --preset, or switch to --preset to streamline setup.

Quick Start

Initialize the skill in a project with a components.json and start adding, searching, and documenting shadcn/ui components.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I automate adding and documenting shadcn/ui components across my codebase?

Automating shadcn/ui workflows involves using a components.json registry to coordinate adding, searching, fixing, and documenting UI components across your project. This streamlines component creation and styling processes.

Can I use shadcn init and preset workflows to streamline UI component setup?

Yes, you can streamline setup by triggering common workflows like shadcn init, init --preset, or switch to --preset. These commands coordinate component creation and project context within a components.json workflow.

What is the best way to manage shadcn/ui component registries and project context?

Managing shadcn/ui registries uses a components.json workflow to coordinate component creation, fixes, debugging, and styling. It provides project context, component docs, and usage examples to accelerate UI development.

Does this workflow require a components.json file to manage shadcn/ui components?

Yes, initializing this workflow requires a project with a components.json file. This registry configuration drives the component management, documentation, and preset switching processes across the codebase.

How do I fix and debug shadcn/ui components within a large project?

Fixing and debugging shadcn/ui components is handled by applying the components.json registry workflow to search, identify, and resolve issues across the codebase. This provides component docs and usage examples to accelerate resolution.