---
description: Brief description shown in /help
argument-hint: <required> [optional]
allowed-tools: Bash(git *), Read, Edit
model: claude-sonnet-4-20250514
disable-model-invocation: false
---

Your prompt template here with $ARGUMENTS or $1, $2, etc.

Variables

Variable	Description	Example
`$ARGUMENTS`	All args as single string	`/cmd foo bar` -> `"foo bar"`
`$1`, `$2`...	Positional args	`/cmd foo bar` -> `$1="foo"`, `$2="bar"`
`@path/file`	Include file contents	`Review @src/main.py`
`!command`	Execute bash, include output	`!git status`

Frontmatter Fields

Field	Purpose	Default
`description`	Shown in /help, enables discoverability	First line of prompt
`argument-hint`	Shows in autocomplete	None
`allowed-tools`	Restrict tool access	Inherits from conversation
`model`	Override model	Inherits from conversation
`disable-model-invocation`	Prevent auto-invocation	`false`

Creation Process

Identify the workflow - What repetitive task needs automation?
Choose scope - Project-specific or personal?
Design the prompt - Keep it focused on one task
Add variables - Use $ARGUMENTS for flexibility
Set frontmatter - Add description and hints
Test and iterate - Refine based on usage

When to Use Slash Commands vs Skills

Use slash commands for:

Quick, single-file prompts
Frequent manual invocations
Simple templates and reminders
Team workflows in version control

Use Skills instead for:

Multi-file resources (scripts, references, assets)
Complex workflows with validation
Capabilities Claude should auto-discover
Detailed procedural knowledge

Best Practices

Meaningful names - /review-pr not /rp
Clear descriptions - Help discoverability in /help
Single responsibility - One task per command
Use argument hints - Guide users on expected input
Version control - Check into git for team sharing
Abstract patterns - Make commands reusable across scenarios

References

Consult these resources when creating slash commands:

examples.md - Read when you need complete working examples or want to show the user reference implementations. Covers git workflows, code review, documentation, testing, scaffolding, and utilities.
patterns.md - Read when implementing specific features: variable handling, file inclusion (@path), bash execution (`!cmd`), tool restrictions, multi-step workflows, or output formatting.
template.md - Starting template for new commands. Copy and customize the structure.

Scope	Location	Label in /help
Project	`.claude/commands/*.md`	(project)
Personal	`~/.claude/commands/*.md`	(user)

slash-command-creator

Slash Command Creator

Quick Reference

File Structure