01
It starts by itself
weekly component sync. Runs in Claude Code routine.
- ↻ weekly component sync
0 9 * * 1
Your parts stay current and your own edits stay safe.
Install the shadcn skill and make it a habit: follow https://gethabit.dev/skills/shadcn-ui/shadcn.md
119K installs126K starsMIT licenceSource on GitHub ↗

shadcn
by shadcn-ui · 119K installs
The skill
Adds and updates shadcn parts in your app.
Only when you ask.
Time saved
Your parts stay current and your own edits stay safe. Less manual work, fewer bugs.
↻ Runs by itselfonce a week
When does it start? How does it check its work? What does it remember?
Stops after 10 components per run, with at most 1 retry.
Run npx shadcn@latest info to get installed components, aliases, base and iconLibrary.
For each component run add with --dry-run to list affected files.
Run add with --diff per file to compare upstream with local.
Take upstream where there are no local changes, and merge by hand where there are.
Ask the user before using --overwrite on any file.
Read changed files, check the critical rules and run the typecheck.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the shadcn skill helps.
No. The skill says to always use the CLI, never raw files.
The loop reads your file and applies upstream changes while keeping yours.
No. Preset switches need your choice of overwrite, partial, merge or skip.
Copy the prompt at the top into your agent. It installs the skill from shadcn-ui/ui and sets up the habit. Or run npx skills add shadcn-ui/ui --skill shadcn.
Yes. It is published under MIT. Habit is free too.
Install the shadcn skill and make it a habit: follow https://gethabit.dev/skills/shadcn-ui/shadcn.md
All shadcn-ui skills →More design skills →
Works in
Made by shadcn-ui, published under MIT. Habit links to the original and never changes it. Is this your skill?