Slash commands

Reusable prompts as /commands you and your team share.

Capture repeated prompts as slash commands. Share them across a team, scope them per project, and chain them into bigger workflows.

All slash commands questions (3)

How do I add my own /command to Claude Code?

Drop a SKILL.md file in .claude/skills/your-command/. Edits hot-reload in the current session, but creating the skills directory for the first time needs a restart. Slash commands and skills are now the same feature; the .claude/commands/ path still works but skills add the features you actually want.
How do I pass arguments to my custom slash command?

Use `$ARGUMENTS` for the whole input, `$0`/`$1`/`$ARGUMENTS[N]` for positional, or named placeholders via the `arguments` frontmatter list. Multi-word values need quotes. Inline `!`shell`` expands before Claude sees the prompt unless you have disabled skill shell execution.
How do I share my Claude Code setup as a plugin with one config file?

Plugins are how you turn `.claude/` into something a teammate installs with one slash command. Two config files (`plugin.json` + `marketplace.json`), one git repo, one `/plugin install`. Plus the namespacing rule that surprises people and the version-pinning trap that quietly stops updates.