slash-command-factory

Slash Command Factory

A comprehensive system for generating production-ready Claude Code slash commands through a simple question-based workflow.

What This Skill Does

This skill helps you create custom slash commands for Claude Code by:

• Asking 5-7 straightforward questions about your command needs
• Generating complete command .md files with proper YAML frontmatter
• Providing 10 powerful preset commands for common use cases
• Validating command format and syntax
• Creating well-organized folder structures
• Offering installation guidance

Output: Complete slash commands ready to use in Claude Code

Official Command Structure Patterns

This skill generates commands following three official patterns from Anthropic documentation:

Pattern A: Simple (Context → Task)

Best for: Straightforward tasks with clear input/output Example: Code review, file updates, simple analysis Official Reference: code-review.md

Structure:

---
allowed-tools: Bash(git diff:*), Bash(git log:*)
description: Purpose description
---

## Context
- Current state: !`bash command`
- Additional data: !`another command`

## Your task
[Clear instructions with numbered steps]
[Success criteria]

When to use:

• Simple, focused tasks
• Quick analysis or reviews
• Straightforward workflows
• 1-3 bash commands for context

Pattern B: Multi-Phase (Discovery → Analysis → Task)

Best for: Complex discovery and documentation tasks Example: Codebase analysis, comprehensive audits, system mapping Official Reference: codebase-analysis.md

Structure:

---
allowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*)
description: Comprehensive purpose
---

# Command Title

## Phase 1: Project Discovery
### Directory Structure
!`find . -type d | sort`

### File Count Analysis
!`find . -type f | wc -l`

## Phase 2: Detailed Analysis
[More discovery commands]
[File references with @]

## Phase 3: Your Task
Based on all discovered information, create:

1. **Deliverable 1**
   - Subsection
   - Details

2. **Deliverable 2**
   - Subsection
   - Details

At the end, write output to [filename].md

When to use:

• Comprehensive analysis needed
• Multiple discovery phases
• Large amounts of context gathering
• 10+ bash commands for data collection
• Generate detailed documentation files

Pattern C: Agent-Style (Role → Process → Guidelines)

Best for: Specialized expert roles and coordination Example: Domain experts, orchestrators, specialized advisors Official Reference: openapi-expert.md

Structure:

---
name: command-name
description: |
  Multi-line description for complex purpose
  explaining specialized role
color: yellow
---

You are a [specialized role] focusing on [domain expertise].

**Core Responsibilities:**

1. **Responsibility Area 1**
   - Specific tasks
   - Expected outputs

2. **Responsibility Area 2**
   - Specific tasks
   - Expected outputs

**Working Process:**

1. [Step 1 in workflow]
2. [Step 2 in workflow]
3. [Step 3 in workflow]

**Important Considerations:**

- [Guideline 1]
- [Guideline 2]
- [Constraint or best practice]

When you encounter [scenario], [action to take].

When to use:

• Need specialized domain expertise
• Orchestrating complex workflows
• Coordinating multiple sub-processes
• Acting as expert advisor
• Require specific procedural guidelines

Comprehensive Naming Convention

Command File Naming Rules

All slash command files MUST follow kebab-case convention:

Format: [verb]-[noun].md, [noun]-[verb].md, or [domain]-[action].md

Rules:

1. Case: Lowercase only with hyphens as separators
2. Length: 2-4 words maximum
3. Characters: Only [a-z0-9-] allowed (letters, numbers, hyphens)
4. Start/End: Must begin and end with letter or number (not hyphen)
5. No: Spaces, underscores, camelCase, TitleCase, or special characters

Conversion Algorithm

User Input → Command Name

Input: "Analyze customer feedback and generate insights"
↓
1. Extract action: "analyze"
2. Extract target: "feedback"
3. Combine: "analyze-feedback"
4. Validate: Matches [a-z0-9-]+ pattern ✓
5. Output: analyze-feedback.md

More Examples:

• "Review pull requests" → pr-review.md or review-pr.md
• "Generate API documentation" → api-document.md or document-api.md
• "Update README files" → update-readme.md or readme-update.md
• "Audit security compliance" → security-audit.md or compliance-audit.md
• "Research market trends" → research-market.md or market-research.md
• "Analyze code quality" → code-analyze.md or analyze-code.md

Official Examples (From Anthropic Docs)

Correct:

• ✅ code-review.md (verb-noun)
• ✅ codebase-analysis.md (noun-noun compound)
• ✅ update-claude-md.md (verb-noun-qualifier)
• ✅ openapi-expert.md (domain-role)

Incorrect:

• ❌ code_review.md (snake_case - wrong)
• ❌ CodeReview.md (PascalCase - wrong)
• ❌ codeReview.md (camelCase - wrong)
• ❌ review.md (too vague - needs target)
• ❌ analyze-customer-feedback-data.md (too long - >4 words)

Bash Permission Patterns

Critical Rule: No Wildcards

❌ NEVER ALLOWED:

allowed-tools: Bash

This wildcard permission is prohibited per official Anthropic patterns.

✅ ALWAYS REQUIRED:

allowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*)

Must specify exact commands with wildcards only for subcommands.

Official Permission Patterns

Based on Anthropic's documented examples:

Git Operations (code-review, update-docs):

allowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git branch:*), Bash(git add:*), Bash(git commit:*)

File Discovery (codebase-analysis):

allowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(du:*)

Content Analysis (comprehensive discovery):

allowed-tools: Bash(grep:*), Bash(wc:*), Bash(head:*), Bash(tail:*), Bash(cat:*)

Data Processing (custom analysis):

allowed-tools: Bash(awk:*), Bash(sed:*), Bash(sort:*), Bash(uniq:*)

Combined Patterns (multi-phase commands):

allowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*), Bash(head:*), Bash(tail:*), Bash(cat:*), Bash(touch:*)

Permission Selection Guide

| Command Type | Bash Permissions | Example Commands | |--------------|------------------|------------------| | Git Commands | git status, git diff, git log, git branch | code-review, commit-assist | | Discovery | find, tree, ls, du | codebase-analyze, structure-map | | Analysis | grep, wc, head, tail, cat | search-code, count-lines | | Update | git diff, find, grep | update-docs, sync-config | | Data Processing | awk, sed, sort, uniq | parse-data, format-output | | Comprehensive | All of the above | full-audit, system-analyze |

Two Paths to Generate Commands

Path 1: Quick-Start Presets (30 seconds)

Choose from 10 powerful preset commands:

Business & Research:

1. /research-business - Comprehensive market research and competitive analysis
2. /research-content - Multi-platform content trend analysis and SEO strategy

Healthcare & Compliance:

1. /medical-translate - Translate medical terminology to 8th-10th grade (German/English)
2. /compliance-audit - HIPAA/GDPR/DSGVO compliance validation

Development & Integration:

1. /api-build - Generate complete API integration code with tests
2. /test-auto - Auto-generate comprehensive test suites

Documentation & Knowledge:

1. /docs-generate - Automated documentation creation
2. /knowledge-mine - Extract and structure insights from documents

Workflow & Productivity:

1. /workflow-analyze - Analyze and optimize business processes
2. /batch-agents - Lau