Reinstall shadcn/ui via the official CLI with confirmation-gated file changes.
npx skills add https://github.com/korwlik23/skills --skill shadcn-reinstall
Please help me install this Agent Skill. Skill: shadcn-reinstall Source: https://github.com/korwlik23/skills/tree/main/v1/shadcn-reinstall Command: npx skills add https://github.com/korwlik23/skills --skill shadcn-reinstall
This skill helps you recover from risky shadcn/ui state drift by planning a safe reinstall path while preventing accidental loss of customized components and uncommitted changes.
Ask an AI agent to run the shadcn-reinstall skill to audit your project, present a deletion/reinstall plan, then reinstall shadcn/ui safely using the official CLI and verify the result.
High-intent search queries and answers about installing and using this skill.
To reinstall shadcn/ui safely, you must audit the project's git status and components.json to identify shadcn-owned files, then use confirmation gates before deleting and regenerating components via the official CLI. This prevents accidental loss of your customized UI files.
Fixing broken component imports after a shadcn/ui upgrade requires an evidence-based reinstall workflow that inspects your UI and utility paths, removes confirmed shadcn-generated files, and regenerates them using the official shadcn init and add CLI commands.
Resetting your frontend UI with a wiped components.json involves inspecting your project's actual file structure to find shadcn-owned surfaces, confirming the deletion scope, and reinitializing the shadcn configuration safely via the official CLI to restore your setup.
Yes, you can safely rename the cn utility during a shadcn reset by operating within a user-approved scope, ensuring the change is verified through lint, typecheck, and build processes to maintain correct component imports.
Yes, the shadcn reinstall process works with React and Next.js frontend projects, targeting environments that need a safe UI reset, cleanup, or correction after broken imports or utility namespace changes.
You should use a confirmation-gated workflow for shadcn dependency safety because it detects the shadcn-owned surface and explicitly asks before deleting, overwriting, or reinitializing critical files, preventing destructive unintended state drift.
porcupine-mdRoute frontend task intents to library SKILL.md paths without executing code.
ionmidoriCreate React UI components with Tailwind CSS, cva, and cn utility.
MohammedSaudAlsahliManage shadcn/ui components and projects via CLI commands.
dmckeeSFUpload files to Salesforce ContentVersion via the upload() API.
