command-creator

# Command Creator Create Claude Code custom slash commands with proper structure and best practices. ## Understanding Commands Claude Code commands are Markdown files with YAML frontmatter that define reusable workflows invoked via `/command-name`. They live in specific locations depending on scope: - **Project-level**: `.claude/commands/` in the project root (shared via git) - **User-level**: `~/.claude/commands/` (personal, available everywhere) - **Categorized**: Nest under subdirectories for namespacing (e.g., `gh/review-pr.md` becomes `/gh:review-pr`) ## Process ### 1. Clarify Intent Before writing anything, understand: - What should the command do? (single clear purpose) - Who uses it — just this user, or the whole team? (determines project vs user-level) - Does it need arguments? What kind? - What tools does it need access to? - Is there a category it belongs to? (e.g., `gh` for GitHub, `cc` for Claude Code meta-commands) ### 2. Write the Command Every command file follows this structure: ```markdown --- description: Brief description shown in command list argument-hint: [expected-arguments] allowed-tools: Tool1, Tool2, Bash(prefix:*) --- # Command Name What this command does and when to use it. ## Process: Step-by-step instructions for the agent to follow. ## Your Task: Act on "$ARGUMENTS" following these guidelines. ``` #### Frontmatter fields | Field | Required | Purpose | |-------|----------|---------| | `description` | Yes | Short description sho...