Command Creator

Slash commands are markdown files in .claude/commands/ (project) or ~/.claude/commands/ (global) that expand into prompts when invoked.

Command Structure

CODEBLOCK0

Creation Workflow

Step 1: Determine Location

1. 1. Check if in git repo: INLINECODE2
2. Default: Git repo → .claude/commands/, No git → INLINECODE4
3. Override if user explicitly says "global" or "project"

Report chosen location before proceeding.

Step 2: Identify Pattern

Load references/patterns.md and present options:

Ask: "Which pattern is closest to what you want?"

Step 3: Gather Information

A. Name and Purpose

• - "What should the command be called?" (kebab-case: my-command)
• "What does it do?" (for description field)

B. Arguments

• - "Does it take arguments? Required or optional?"
• Required: <placeholder>, Optional: INLINECODE7

C. Workflow Steps

• - "What specific steps should it follow?"
• "What tools or commands should it use?"

D. Constraints

• - "Any specific tools to use or avoid?"
• "Any files to read for context?"

Step 4: Generate Command

Load references/best-practices.md for:

• - Template structure
• Writing style (imperative form)
• Quality checklist

Key principles:

• - Use imperative form: "Run X", not "You should run X"
• Be explicit: "Run make lint", not "Check for errors"
• Include expected outcomes
• Define error handling
• State success criteria

Step 5: Create File

CODEBLOCK1

Write the command file. Report:

• - File location
• What the command does
• How to use: INLINECODE9

Step 6: Test (Optional)

Suggest: "Test with /command-name [args]"

Iterate based on feedback.

Writing Guidelines

Imperative form (verb-first):

• - ✅ "Run git status"
• ❌ "You should run git status"

Specific, not vague:

• - ✅ "Run make lint to check for errors"
• ❌ "Check for errors"

Include outcomes:

• - ✅ "Run git status - should show modified files"
• ❌ "Run git status"

Realistic examples:

• - ✅ INLINECODE13
• ❌ INLINECODE14

Command Patterns Quick Reference

Workflow Automation

Iterative Fixing

Agent Delegation

See references/examples.md for full command examples.

Quality Checklist

Before finalizing:

• - [ ] Name is kebab-case (my-command, not my_command)
• [ ] Description is action-oriented
• [ ] Steps are numbered and specific
• [ ] Tool usage explicitly specified
• [ ] Error handling defined
• [ ] Success criteria stated
• [ ] Uses imperative form

NEVER

• - Use underscores in command names (use hyphens)
• Write vague instructions ("fix errors")
• Skip error handling
• Use second person ("You should...")
• Create commands without testing
• Leave success criteria undefined