create-command

To create reusable slash commands in Claude Code, you generate markdown files under the .claude/commands directory. These files act as prompt shortcuts, invoked via /name, and support $ARGUMENTS placeholders for dynamic inputs.

Multi-step command templates for Claude workflows are structured as markdown files with optional YAML frontmatter for descriptions. You can define multi-step prompt instructions and use $ARGUMENTS placeholders to pass dynamic values when invoking the shortcut.

Yes, $ARGUMENTS placeholders are supported in .claude/commands files. They allow you to pass dynamic arguments into your prompt shortcuts when you invoke the slash command by name inside Claude Code workflows.

To prevent custom prompt shortcuts from being committed to git, use a custom- prefix for your command names. This naming convention designates the slash commands as personal, gitignored files within your workspace.

Claude Code supports agent-invoking shortcuts by generating markdown command files configured to call an agent. During guided creation, you specify whether the command needs an agent, and the template adjusts accordingly.

Slash command files should use lowercase, hyphen-separated names to avoid collisions. The system recommends this standard format, along with a custom- prefix if you want to keep the commands personal and gitignored.