CONCEPT Where the file lives decides who can use it
A command or skill has a scope set entirely by its location on disk. The same
.md file is personal in your home directory and project in a repo — nothing in
the file changes, only the folder. Scope answers one question: who sees this command?
| Scope | Location (command / skill) | Applies to |
|---|---|---|
Personal (user) | ~/.claude/commands/ · ~/.claude/skills/ | All of your projects |
Project (project) | .claude/commands/ · .claude/skills/ | This repo only — commit to share |
| Plugin | <plugin>/skills/<name>/SKILL.md | Wherever that plugin is enabled |
| Enterprise | Managed settings (org-deployed) | All users in the organization |
/ menu the command listing labels a command by its source, e.g.
(user) for a personal command and (project) for a project one, so you can tell at a
glance where a command came from.CONCEPT Plugin commands are namespaced — no clashes
Commands from a plugin are invoked under a plugin-name:command
namespace — e.g. /my-plugin:review. Because the plugin name prefixes the command, a plugin command
cannot collide with your personal or project commands. Personal, project, and enterprise commands
share the bare /name space, so naming order matters there: when the same name
exists at several levels, enterprise overrides personal, and personal overrides project. A skill at any
of these levels also overrides a same-named bundled skill, and a skill wins over a same-named command
file.
DIAGRAM Resolving /deploy
plugin:name"} P -->|"yes"| PL["🔵 Plugin command runs
(its own namespace)"] P -->|"no — bare /deploy"| E{"Enterprise has it?"} E -->|"yes"| ENT["🟣 Enterprise wins"] E -->|"no"| U{"Personal (user) has it?"} U -->|"yes"| USR["🟢 Personal wins over project"] U -->|"no"| PRJ["🟠 Project command runs"] classDef ok fill:#d4edda,stroke:#28a745,color:#155724; classDef pl fill:#cfe2ff,stroke:#0d6efd,color:#084298; classDef prj fill:#ffe8cc,stroke:#ff9f40,color:#9a4a0a; classDef ent fill:#e7d6ff,stroke:#8b5cf6,color:#4c1d95; class USR ok; class PL pl; class PRJ prj; class ENT ent;
CODE The same command at three scopes
One name, three homes. The location — not the contents — determines reach and precedence:
# Personal: available in every project you open — labeled (user) ~/.claude/commands/standup.md # Project: shipped with the repo, shared with the team — labeled (project) <repo>/.claude/commands/standup.md # Plugin: namespaced, invoked as /my-plugin:standup — never clashes my-plugin/skills/standup/SKILL.md # Precedence for the bare name /standup: # enterprise > personal (user) > project # Plugin lives in its own /my-plugin:standup namespace.
TRADE-OFFS Personal vs. project vs. plugin
✅ Reach & sharing
- Personal: follows you everywhere, private
- Project: shared with the team via the repo
- Plugin: distributable to many repos + users, namespaced
⚠️ Cost of that reach
- Personal: teammates don't get it
- Project: only in that repo; needs workspace trust for tools
- Plugin: must be built, published, and enabled
EXAM TRAPS
/deploy." → No — plugin
commands live under a plugin-name: namespace, so they cannot collide with your bare-name
commands.~/.claude/ = personal, repo .claude/ = project, plugin folder = plugin.(user) / (project) label changes what I type." → It is
only a source label in the menu. You still invoke both as /name.PRACTICE
Q1 · You have a personal and a project command both named /deploy. Which runs?
The personal (user) one — for the bare name, personal overrides project (and enterprise overrides personal).
Q2 · How is a plugin's review command invoked, and why can't it clash?
As /my-plugin:review. The plugin-name namespace prefixes it, so it lives in
its own space and never collides with personal or project commands.
Q3 · A teammate needs your /standup command. Where must it live?
In the repo at .claude/commands/standup.md (project scope), committed to
version control. A personal ~/.claude/ copy only works for you.