command-creatorlisted

Authors Claude Code slash commands (`/name [args]` markdown files at `.claude/commands/<name>.md` or `<plugin>/commands/<name>.md`, plus the equivalent `.claude/skills/<name>/SKILL.md` directory format). Use whenever a new slash command is being designed, an existing command is being edited, an argument-driven workflow is being captured, shell injection is being added to gather live context (git diff, PR data, env), multi-phase command bodies are being structured, `argument-hint` and `arguments` frontmatter are being chosen, approval gates with AskUserQuestion are being inserted before destructive actions, or a command that fires the wrong way is being debugged. Triggers on "create a slash command", "build a /command", "add a plugin command", "make a /pr-summary", "write a command body", "shell injection in command", "argument design for command", "fix this command". Use even when the user does not say the word "command" but is asking for `/name` invocation with arguments, a side-effect workflow, or a context
anilcancakir/claude-code · ★ 1 · Code & Development · score 77

Install: claude install-skill anilcancakir/claude-code

# Command Creator You are about to write or edit a Claude Code slash command another Claude will execute. A command is a markdown file that becomes a `/name` invocation: when the user types `/foo bar baz`, Claude Code reads the file, substitutes `$ARGUMENTS` with `bar baz`, runs shell injection blocks, and injects the resulting prompt as a single user message. The model then executes the body as the next turn. This skill is the playbook for designing arguments, shell-injection-driven context gathering, phase-based body structure, approval gates, and the storage-format choice. Target is Opus 4.8. The same shape works for Sonnet 4.6 and Haiku 4.5 at lower effort levels. ## Three jobs, not one Writing a slash command splits into three tasks. Conflating them is the most common authoring mistake. 1. **Surrounding skill shape.** Frontmatter fields, scope (project/user/plugin/managed), invocation control (`disable-model-invocation`, `user-invocable`), `paths:`, `allowed-tools`, `model`, `effort`. Same rules as any skill. Route through `ac:skill-creator` (its body, references, and pre-flight checklist all apply). 2. **Command-specific shape.** Argument design, shell injection for context gathering, phase-based body structure, approval gates, storage format (flat `.md` vs skill-directory). This file teaches that. 3. **Body content.** The markdown the model reads when the command fires. This is a prompt. Route through `ac:prompt-writer` (architecture, snippets, anti-patterns,