Two routes into the same files. A plugin is the easy way and keeps itself updated; a single item is the surgical way when you want one thing in one project.
Bundles of related items managed by Claude Code. Hooks activate on install, commands are namespaced (/security:security-audit), and one command updates everything.
dotclaude
/plugin marketplace add KhaledSaeed18/dotclaude/plugin install engineering@dotclaude/plugin marketplace update dotclaudeA good starter set is engineering, git, security-hooks.
The shadcn CLI copies one item into the project you run it from, under .claude/. Nothing else is touched, and nothing updates itself.
npx shadcn@latest add KhaledSaeed18/dotclaude/academic-writing.claude/ into ~/.claude/: folders for skills and hooks, single files for agents and commands..claude/settings.json; each hook's page shows it.| Plugin | Single item | |
|---|---|---|
| Scope | Everything in the bundle, in every project | One item, in one project |
| Updates | One command updates all installed bundles | Run the add command again to refresh |
| Hooks | Wired on install | Add the settings block yourself |
| Commands | Namespaced: /engineering:research-log | Plain: /research-log |
| Where the files go | Claude Code's plugin cache | .claude/ in the project, visible in git |
| Best for | Your own machine, a whole workflow | A shared repository, one specific need |
Four kinds of file, four ways Claude reaches them.
A procedure Claude loads on its own when your request matches its description. You never call it by name.
Installs to .claude/skills/<name>/
A specialist Claude hands a whole side task to, in its own context, returning only the result.
Installs to .claude/agents/<name>.md
A shortcut you trigger yourself by typing /name in the session.
Installs to .claude/commands/<name>.md
A script that runs on a Claude Code event, every time, with no model judgment involved.
Installs to .claude/hooks/<name>/
Every item is a Markdown file you can read before you trust it: open any item's page and the full text is there, or read it on GitHub. Hooks are small standalone scripts with no dependencies; each hook's page shows exactly what it blocks and allows.
Plugins live in Claude Code's own config and apply wherever you run it. For one project, install the items you want as single items so they sit in that repository's .claude/ folder.
A plugin: /plugin uninstall name@dotclaude. A single item: delete its file or folder under .claude/, and for a hook remove its block from settings.json.
No. The registry format is shadcn's, but the items are plain files; the CLI only copies them into place. Any folder works as the project root.
Skills are plain Markdown with a description and instructions, so most agents that read a skills folder can use them. Hooks, agents and commands follow Claude Code's conventions.