[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F2A2KSBGN0AGXG2DF9XM8Z":3,"skill-same:01M6F2A2KSBGN0AGXG2DF9XM8Z":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6F2A2KSBGN0AGXG2DF9XM8Z","slash-command-factory",null,"Generate custom Claude Code slash commands through intelligent 5-7 question flow. Creates powerful commands for business research, content analysis, healthcare compliance, API integration, documentation automation, and workflow optimization. Outputs organized commands to generated-commands\u002F with validation and installation guidance.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Fslash-command-factory\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"slash command factory","factory","command","healthcare","with","commands","api integration","business","generated","question","workflow","api","analysis","flow","Optimization","workflow optimization","code","generate","documentation","automation","2026-11-10 10:12:30",false,"---\nname: slash-command-factory\ndescription: Generate custom Claude Code slash commands through intelligent 5-7 question flow. Creates powerful commands for business research, content analysis, healthcare compliance, API integration, documentation automation, and workflow optimization. Outputs organized commands to generated-commands\u002F with validation and installation guidance.\n---\n\n# Slash Command Factory\n\nA comprehensive system for generating production-ready Claude Code slash commands through a simple question-based workflow.\n\n---\n\n## What This Skill Does\n\nThis skill helps you create custom slash commands for Claude Code by:\n- Asking 5-7 straightforward questions about your command needs\n- Generating complete command .md files with proper YAML frontmatter\n- Providing 10 powerful preset commands for common use cases\n- Validating command format and syntax\n- Creating well-organized folder structures\n- Offering installation guidance\n\n**Output**: Complete slash commands ready to use in Claude Code\n\n---\n\n## Official Command Structure Patterns\n\nThis skill generates commands following **three official patterns** from Anthropic documentation:\n\n### Pattern A: Simple (Context → Task)\n\n**Best for**: Straightforward tasks with clear input\u002Foutput\n**Example**: Code review, file updates, simple analysis\n**Official Reference**: code-review.md\n\n**Structure**:\n```markdown\n---\nallowed-tools: Bash(git diff:*), Bash(git log:*)\ndescription: Purpose description\n---\n\n## Context\n- Current state: !`bash command`\n- Additional data: !`another command`\n\n## Your task\n[Clear instructions with numbered steps]\n[Success criteria]\n```\n\n**When to use**:\n- Simple, focused tasks\n- Quick analysis or reviews\n- Straightforward workflows\n- 1-3 bash commands for context\n\n---\n\n### Pattern B: Multi-Phase (Discovery → Analysis → Task)\n\n**Best for**: Complex discovery and documentation tasks\n**Example**: Codebase analysis, comprehensive audits, system mapping\n**Official Reference**: codebase-analysis.md\n\n**Structure**:\n```markdown\n---\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*)\ndescription: Comprehensive purpose\n---\n\n# Command Title\n\n## Phase 1: Project Discovery\n### Directory Structure\n!`find . -type d | sort`\n\n### File Count Analysis\n!`find . -type f | wc -l`\n\n## Phase 2: Detailed Analysis\n[More discovery commands]\n[File references with @]\n\n## Phase 3: Your Task\nBased on all discovered information, create:\n\n1. **Deliverable 1**\n   - Subsection\n   - Details\n\n2. **Deliverable 2**\n   - Subsection\n   - Details\n\nAt the end, write output to [filename].md\n```\n\n**When to use**:\n- Comprehensive analysis needed\n- Multiple discovery phases\n- Large amounts of context gathering\n- 10+ bash commands for data collection\n- Generate detailed documentation files\n\n---\n\n### Pattern C: Agent-Style (Role → Process → Guidelines)\n\n**Best for**: Specialized expert roles and coordination\n**Example**: Domain experts, orchestrators, specialized advisors\n**Official Reference**: openapi-expert.md\n\n**Structure**:\n```markdown\n---\nname: command-name\ndescription: |\n  Multi-line description for complex purpose\n  explaining specialized role\ncolor: yellow\n---\n\nYou are a [specialized role] focusing on [domain expertise].\n\n**Core Responsibilities:**\n\n1. **Responsibility Area 1**\n   - Specific tasks\n   - Expected outputs\n\n2. **Responsibility Area 2**\n   - Specific tasks\n   - Expected outputs\n\n**Working Process:**\n\n1. [Step 1 in workflow]\n2. [Step 2 in workflow]\n3. [Step 3 in workflow]\n\n**Important Considerations:**\n\n- [Guideline 1]\n- [Guideline 2]\n- [Constraint or best practice]\n\nWhen you encounter [scenario], [action to take].\n```\n\n**When to use**:\n- Need specialized domain expertise\n- Orchestrating complex workflows\n- Coordinating multiple sub-processes\n- Acting as expert advisor\n- Require specific procedural guidelines\n\n---\n\n## Comprehensive Naming Convention\n\n### Command File Naming Rules\n\nAll slash command files MUST follow kebab-case convention:\n\n**Format**: `[verb]-[noun].md`, `[noun]-[verb].md`, or `[domain]-[action].md`\n\n**Rules**:\n1. **Case**: Lowercase only with hyphens as separators\n2. **Length**: 2-4 words maximum\n3. **Characters**: Only `[a-z0-9-]` allowed (letters, numbers, hyphens)\n4. **Start\u002FEnd**: Must begin and end with letter or number (not hyphen)\n5. **No**: Spaces, underscores, camelCase, TitleCase, or special characters\n\n---\n\n### Conversion Algorithm\n\n**User Input** → **Command Name**\n\n```\nInput: \"Analyze customer feedback and generate insights\"\n↓\n1. Extract action: \"analyze\"\n2. Extract target: \"feedback\"\n3. Combine: \"analyze-feedback\"\n4. Validate: Matches [a-z0-9-]+ pattern ✓\n5. Output: analyze-feedback.md\n```\n\n**More Examples**:\n- \"Review pull requests\" → `pr-review.md` or `review-pr.md`\n- \"Generate API documentation\" → `api-document.md` or `document-api.md`\n- \"Update README files\" → `update-readme.md` or `readme-update.md`\n- \"Audit security compliance\" → `security-audit.md` or `compliance-audit.md`\n- \"Research market trends\" → `research-market.md` or `market-research.md`\n- \"Analyze code quality\" → `code-analyze.md` or `analyze-code.md`\n\n---\n\n### Official Examples (From Anthropic Docs)\n\n**Correct**:\n- ✅ `code-review.md` (verb-noun)\n- ✅ `codebase-analysis.md` (noun-noun compound)\n- ✅ `update-claude-md.md` (verb-noun-qualifier)\n- ✅ `openapi-expert.md` (domain-role)\n\n**Incorrect**:\n- ❌ `code_review.md` (snake_case - wrong)\n- ❌ `CodeReview.md` (PascalCase - wrong)\n- ❌ `codeReview.md` (camelCase - wrong)\n- ❌ `review.md` (too vague - needs target)\n- ❌ `analyze-customer-feedback-data.md` (too long - >4 words)\n\n---\n\n## Bash Permission Patterns\n\n### Critical Rule: No Wildcards\n\n**❌ NEVER ALLOWED**:\n```yaml\nallowed-tools: Bash\n```\nThis wildcard permission is **prohibited** per official Anthropic patterns.\n\n**✅ ALWAYS REQUIRED**:\n```yaml\nallowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*)\n```\nMust specify **exact commands** with wildcards only for subcommands.\n\n---\n\n### Official Permission Patterns\n\nBased on Anthropic's documented examples:\n\n**Git Operations** (code-review, update-docs):\n```yaml\nallowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git branch:*), Bash(git add:*), Bash(git commit:*)\n```\n\n**File Discovery** (codebase-analysis):\n```yaml\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(du:*)\n```\n\n**Content Analysis** (comprehensive discovery):\n```yaml\nallowed-tools: Bash(grep:*), Bash(wc:*), Bash(head:*), Bash(tail:*), Bash(cat:*)\n```\n\n**Data Processing** (custom analysis):\n```yaml\nallowed-tools: Bash(awk:*), Bash(sed:*), Bash(sort:*), Bash(uniq:*)\n```\n\n**Combined Patterns** (multi-phase commands):\n```yaml\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*), Bash(head:*), Bash(tail:*), Bash(cat:*), Bash(touch:*)\n```\n\n---\n\n### Permission Selection Guide\n\n| Command Type | Bash Permissions | Example Commands |\n|--------------|------------------|------------------|\n| **Git Commands** | `git status, git diff, git log, git branch` | code-review, commit-assist |\n| **Discovery** | `find, tree, ls, du` | codebase-analyze, structure-map |\n| **Analysis** | `grep, wc, head, tail, cat` | search-code, count-lines |\n| **Update** | `git diff, find, grep` | update-docs, sync-config |\n| **Data Processing** | `awk, sed, sort, uniq` | parse-data, format-output |\n| **Comprehensive** | All of the above | full-audit, system-analyze |\n\n---\n\n## Two Paths to Generate Commands\n\n### Path 1: Quick-Start Presets (30 seconds)\n\nChoose from 10 powerful preset commands:\n\n**Business & Research**:\n1. **\u002Fresearch-business** - Comprehensive market research and competitive analysis\n2. **\u002Fresearch-content** - Multi-platform content trend analysis and SEO strategy\n\n**Healthcare & Compliance**:\n3. **\u002Fmedical-translate** - Translate medical terminology to 8th-10th grade (German\u002FEnglish) \n4. **\u002Fcompliance-audit** - HIPAA\u002FGDPR\u002FDSGVO compliance validation\n\n**Development & Integration**:\n5. **\u002Fapi-build** - Generate complete API integration code with tests\n6. **\u002Ftest-auto** - Auto-generate comprehensive test suites\n\n**Documentation & Knowledge**:\n7. **\u002Fdocs-generate** - Automated documentation creation\n8. **\u002Fknowledge-mine** - Extract and structure insights from documents\n\n**Workflow & Productivity**:\n9. **\u002Fworkflow-analyze** - Analyze and optimize business processes\n10. **\u002Fbatch-agents** - Launch and coordinate multiple agents for complex tasks\n\n### Path 2: Custom Command (5-7 Questions)\n\nCreate a completely custom command for your specific needs.\n\n---\n\n## Question Flow (Custom Path)\n\n### Question 1: Command Purpose\n\n\"What should this slash command do?\n\nBe specific about its purpose and when you'll use it.\n\nExamples:\n- 'Analyze customer feedback and generate actionable insights'\n- 'Generate HIPAA-compliant API documentation'\n- 'Research market trends and create content strategy'\n- 'Extract key insights from research papers'\n\nYour command's purpose: ___\"\n\n---\n\n### Question 2: Arguments (Auto-Determined)\n\nThe skill automatically determines if your command needs arguments based on the purpose.\n\n**If arguments are needed**, they will use `$ARGUMENTS` format:\n- User types: `\u002Fyour-command argument1 argument2`\n- Command receives: `$ARGUMENTS` = \"argument1 argument2\"\n\n**Examples**:\n- `\u002Fresearch-business \"Tesla\" \"EV market\"` → $ARGUMENTS = \"Tesla EV market\"\n- `\u002Fmedical-translate \"Myokardinfarkt\" \"de\"` → $ARGUMENTS = \"Myokardinfarkt de\"\n\n**No user input needed** - skill decides intelligently.\n\n---\n\n### Question 3: Which Tools?\n\n\"Which Claude Code tools should this command use?\n\nAvailable tools:\n- **Read** - Read files\n- **Write** - Create files\n- **Edit** - Modify files\n- **Bash** - Execute shell commands (MUST specify exact commands)\n- **Grep** - Search code\n- **Glob** - Find files by pattern\n- **Task** - Launch agents\n\n**CRITICAL**: For Bash, you MUST specify exact commands, not wildcards.\n\n**Bash Examples**:\n- ✅ Bash(git status:*), Bash(git diff:*), Bash(git log:*)\n- ✅ Bash(find:*), Bash(tree:*), Bash(ls:*)\n- ✅ Bash(grep:*), Bash(wc:*), Bash(head:*)\n- ❌ Bash (wildcard not allowed per official patterns)\n\n**Tool Combination Examples**:\n- Git command: Read, Bash(git status:*), Bash(git diff:*)\n- Code generator: Read, Write, Edit\n- Discovery command: Bash(find:*), Bash(tree:*), Bash(grep:*)\n- Analysis command: Read, Grep, Task (launch agents)\n\nYour tools (comma-separated): ___\"\n\n---\n\n### Question 4: Agent Integration\n\n\"Does this command need to launch agents for specialized tasks?\n\nExamples of when to use agents:\n- Complex analysis (launch rr-architect, rr-security)\n- Implementation tasks (launch rr-frontend, rr-backend)\n- Quality checks (launch rr-qa, rr-test-runner)\n\nOptions:\n1. **No agents** - Command handles everything itself\n2. **Launch agents** - Delegate to specialized agents\n\nYour choice (1 or 2): ___\"\n\nIf \"2\", ask: \"Which agents should it launch? ___\"\n\n---\n\n### Question 5: Output Type\n\n\"What type of output should this command produce?\n\n1. **Analysis** - Research report, insights, recommendations\n2. **Files** - Generated code, documentation, configs\n3. **Action** - Execute tasks, run workflows, deploy\n4. **Report** - Structured report with findings and next steps\n\nYour choice (1, 2, 3, or 4): ___\"\n\n---\n\n### Question 6: Model Preference (Optional)\n\n\"Which Claude model should this command use?\n\n1. **Default** - Inherit from main conversation (recommended)\n2. **Sonnet** - Best for complex tasks\n3. **Haiku** - Fastest, cheapest (for simple commands)\n4. **Opus** - Maximum capability (for critical tasks)\n\nYour choice (1, 2, 3, or 4) or press Enter for default: ___\"\n\n---\n\n### Question 7: Additional Features (Optional)\n\n\"Any special features?\n\nOptional features:\n- **Bash execution** - Run shell commands and include output (!`command`)\n- **File references** - Include file contents (@file.txt)\n- **Context gathering** - Read project files for context\n\nFeatures you need (comma-separated) or press Enter to skip: ___\"\n\n---\n\n## Generation Process\n\nAfter collecting answers:\n\n1. **Generate YAML Frontmatter**:\n```yaml\n---\ndescription: [From command purpose]\nargument-hint: [If $ARGUMENTS needed]\nallowed-tools: [From tool selection]\nmodel: [If specified]\n---\n```\n\n2. **Generate Command Body**:\n```markdown\n[Purpose-specific instructions]\n\n[If uses agents]:\n1. **Launch [agent-name]** with [specific task]\n2. Coordinate workflow\n3. Validate results\n\n[If uses bash]:\n- Context: !`bash command`\n\n[If uses file refs]:\n- Review: @file.txt\n\nSuccess Criteria: [Based on output type]\n```\n\n3. **Create Folder Structure**:\n```\ngenerated-commands\u002F[command-name]\u002F\n├── [command-name].md    # Command file (ROOT)\n├── README.md            # Installation guide (ROOT)\n├── TEST_EXAMPLES.md     # Testing examples (ROOT)\n└── [folders if needed]  # standards\u002F, examples\u002F, scripts\u002F\n```\n\n4. **Validate Format**:\n- ✅ YAML frontmatter valid\n- ✅ $ARGUMENTS syntax correct (if used)\n- ✅ allowed-tools format proper\n- ✅ Folder organization clean\n\n5. **Provide Installation Instructions**:\n```\nYour command is ready!\n\nOutput location: generated-commands\u002F[command-name]\u002F\n\nTo install:\n1. Copy the command file:\n   cp generated-commands\u002F[command-name]\u002F[command-name].md .claude\u002Fcommands\u002F\n\n2. Restart Claude Code (if already running)\n\n3. Test:\n   \u002F[command-name] [arguments]\n```\n\n---\n\n## Preset Command Details\n\n### 1. \u002Fresearch-business\n\n**Purpose**: Comprehensive business and market research\n\n**Arguments**: `$ARGUMENTS` (company or market to research)\n\n**YAML**:\n```yaml\n---\ndescription: Comprehensive business and market research with competitor analysis\nargument-hint: [company\u002Fmarket] [industry]\nallowed-tools: Read, Bash, Grep\n---\n```\n\n**What it does**:\n- Market size and trends analysis\n- Competitor SWOT analysis\n- Opportunity identification\n- Industry landscape overview\n- Strategic recommendations\n\n---\n\n### 2. \u002Fresearch-content\n\n**Purpose**: Multi-platform content trend analysis\n\n**Arguments**: `$ARGUMENTS` (topic to research)\n\n**YAML**:\n```yaml\n---\ndescription: Multi-platform content trend analysis for data-driven content strategy\nargument-hint: [topic] [platforms]\nallowed-tools: Read, Bash\n---\n```\n\n**What it does**:\n- Analyze trends across Google, Reddit, YouTube, Medium, LinkedIn, X\n- User intent analysis (informational, commercial, transactional)\n- Content gap identification\n- SEO-optimized outline generation\n- Platform-specific publishing strategies\n\n---\n\n### 3. \u002Fmedical-translate\n\n**Purpose**: Translate medical terminology to patient-friendly language\n\n**Arguments**: `$ARGUMENTS` (medical term and language)\n\n**YAML**:\n```yaml\n---\ndescription: Translate medical terminology to 8th-10th grade reading level (German\u002FEnglish)\nargument-hint: [medical-term] [de|en]\nallowed-tools: Read\n---\n```\n\n**What it does**:\n- Translate complex medical terms\n- Simplify to 8th-10th grade reading level\n- Validate with Flesch-Kincaid (EN) or Wiener Sachtextformel (DE)\n- Preserve clinical accuracy\n- Provide patient-friendly explanations\n\n---\n\n### 4. \u002Fcompliance-audit\n\n**Purpose**: Check code for regulatory compliance\n\n**Arguments**: `$ARGUMENTS` (path and compliance standard)\n\n**YAML**:\n```yaml\n---\ndescription: Audit code for HIPAA\u002FGDPR\u002FDSGVO compliance requirements\nargument-hint: [code-path] [hipaa|gdpr|dsgvo|all]\nallowed-tools: Read, Grep, Task\n---\n```\n\n**What it does**:\n- Scan for PHI\u002FPII handling\n- Check encryption requirements\n- Verify audit logging\n- Validate data subject rights\n- Generate compliance report\n\n---\n\n### 5. \u002Fapi-build\n\n**Purpose**: Generate complete API integration code\n\n**Arguments**: `$ARGUMENTS` (API name and endpoints)\n\n**YAML**:\n```yaml\n---\ndescription: Generate complete API client with error handling and tests\nargument-hint: [api-name] [endpoints]\nallowed-tools: Read, Write, Edit, Bash, Task\n---\n```\n\n**What it does**:\n- Generate API client classes\n- Add error handling and retries\n- Create authentication logic\n- Generate unit and integration tests\n- Add usage documentation\n\n---\n\n### 6. \u002Ftest-auto\n\n**Purpose**: Auto-generate comprehensive test suites\n\n**Arguments**: `$ARGUMENTS` (file path and test type)\n\n**YAML**:\n```yaml\n---\ndescription: Auto-generate comprehensive test suite with coverage analysis\nargument-hint: [file-path] [unit|integration|e2e]\nallowed-tools: Read, Write, Bash\n---\n```\n\n**What it does**:\n- Analyze code to test\n- Generate test cases (happy path, edge cases, errors)\n- Add test fixtures and mocks\n- Calculate coverage\n- Provide testing documentation\n\n---\n\n### 7. \u002Fdocs-generate\n\n**Purpose**: Automated documentation generation\n\n**Arguments**: `$ARGUMENTS` (code path and doc type)\n\n**YAML**:\n```yaml\n---\ndescription: Auto-generate documentation from code (API docs, README, architecture)\nargument-hint: [code-path] [api|readme|architecture|all]\nallowed-tools: Read, Write, Grep\n---\n```\n\n**What it does**:\n- Extract code structure and functions\n- Generate API documentation\n- Create README with usage examples\n- Build architecture diagrams (Mermaid)\n- Add code examples\n\n---\n\n### 8. \u002Fknowledge-mine\n\n**Purpose**: Extract structured insights from documents\n\n**Arguments**: `$ARGUMENTS` (document path and output format)\n\n**YAML**:\n```yaml\n---\ndescription: Extract and structure knowledge from documents into actionable insights\nargument-hint: [doc-path] [faq|summary|kb|all]\nallowed-tools: Read, Grep\n---\n```\n\n**What it does**:\n- Read and analyze documents\n- Extract key insights\n- Generate FAQs\n- Create knowledge base articles\n- Summarize findings\n\n---\n\n### 9. \u002Fworkflow-analyze\n\n**Purpose**: Analyze and optimize business workflows\n\n**Arguments**: `$ARGUMENTS` (workflow description)\n\n**YAML**:\n```yaml\n---\ndescription: Analyze workflows and provide optimization recommendations\nargument-hint: [workflow-description]\nallowed-tools: Read, Task\n---\n```\n\n**What it does**:\n- Map current workflow\n- Identify bottlenecks\n- Suggest automation opportunities\n- Calculate efficiency gains\n- Create implementation roadmap\n\n---\n\n### 10. \u002Fbatch-agents\n\n**Purpose**: Launch multiple coordinated agents\n\n**Arguments**: `$ARGUMENTS` (agent names and task)\n\n**YAML**:\n```yaml\n---\ndescription: Launch and coordinate multiple agents for complex tasks\nargument-hint: [agent-names] [task-description]\nallowed-tools: Task\n---\n```\n\n**What it does**:\n- Parse agent list\n- Launch agents in parallel (if safe) or sequential\n- Coordinate outputs\n- Integrate results\n- Provide comprehensive summary\n\n---\n\n## Output Structure\n\nCommands are generated in your project's root directory:\n\n```\n[your-project]\u002F\n└── generated-commands\u002F\n    └── [command-name]\u002F\n        ├── [command-name].md      # Command file (ROOT level)\n        ├── README.md              # Installation guide (ROOT level)\n        ├── TEST_EXAMPLES.md       # Testing guide (ROOT level - if applicable)\n        │\n        ├── standards\u002F             # Only if command has standards\n        ├── examples\u002F              # Only if command has examples\n        └── scripts\u002F               # Only if command has helper scripts\n```\n\n**Organization Rules**:\n- All .md files in ROOT directory\n- Supporting folders separate (standards\u002F, examples\u002F, scripts\u002F)\n- No mixing of different types in same folder\n- Clean, hierarchical structure\n\n---\n\n## Installation\n\n**After generation**:\n\n1. **Review output**:\n   ```bash\n   ls generated-commands\u002F[command-name]\u002F\n   ```\n\n2. **Copy to Claude Code** (when ready):\n   ```bash\n   # Project-level (this project only)\n   cp generated-commands\u002F[command-name]\u002F[command-name].md .claude\u002Fcommands\u002F\n\n   # User-level (all projects)\n   cp generated-commands\u002F[command-name]\u002F[command-name].md ~\u002F.claude\u002Fcommands\u002F\n   ```\n\n3. **Restart Claude Code** (if running)\n\n4. **Test command**:\n   ```bash\n   \u002F[command-name] [arguments]\n   ```\n\n---\n\n## Usage Examples\n\n### Generate a Preset Command\n\n```\n@slash-command-factory\n\nUse the \u002Fresearch-business preset\n```\n\n**Output**: Complete business research command ready to install\n\n---\n\n### Generate a Custom Command\n\n```\n@slash-command-factory\n\nCreate a custom command for analyzing customer feedback and generating product insights\n```\n\n**Skill asks 5-7 questions** → **Generates complete command** → **Validates format** → **Provides installation steps**\n\n---\n\n## Command Format (What Gets Generated)\n\n**Example generated command** (`my-command.md`):\n\n```markdown\n---\ndescription: Brief description of what the command does\nargument-hint: [arg1] [arg2]\nallowed-tools: Read, Write, Bash\nmodel: claude-3-5-sonnet-20241022\n---\n\n# Command Instructions\n\nDo [task] with \"$ARGUMENTS\":\n\n1. **Step 1**: First action\n2. **Step 2**: Second action\n3. **Step 3**: Generate output\n\n**Success Criteria**:\n- Criterion 1\n- Criterion 2\n- Criterion 3\n```\n\n---\n\n## Validation\n\nEvery generated command is automatically validated for:\n- ✅ Valid YAML frontmatter (proper syntax, required fields)\n- ✅ Correct argument format ($ARGUMENTS, not $1 $2 $3)\n- ✅ allowed-tools syntax (comma-separated string)\n- ✅ Clean folder organization (if folders used)\n- ✅ No placeholder text\n\n**If validation fails**, you'll get specific fix instructions.\n\n---\n\n## Best Practices\n\n**For Command Design**:\n- Keep commands focused (one clear purpose)\n- Use descriptive names (kebab-case for files)\n- Document expected arguments clearly\n- Include success criteria\n- Add examples in TEST_EXAMPLES.md\n\n**For Tool Selection**:\n- Read: For analyzing files\n- Write\u002FEdit: For generating\u002Fmodifying files\n- Bash: For system commands, web research\n- Task: For launching agents\n- Grep\u002FGlob: For searching code\n\n**For Agent Integration**:\n- Use Task tool to launch agents\n- Specify which agents clearly\n- Coordinate outputs\n- Document agent roles\n\n---\n\n## Important Notes\n\n**Arguments**:\n- ✅ Always use `$ARGUMENTS` (all arguments as one string)\n- ❌ Never use `$1`, `$2`, `$3` (positional - not used by this factory)\n\n**Folder Organization**:\n- ✅ All .md files in command root directory\n- ✅ Supporting folders separate (standards\u002F, examples\u002F, scripts\u002F)\n- ✅ No mixing of different types\n\n**Output Location**:\n- Commands generate to: `.\u002Fgenerated-commands\u002F[command-name]\u002F`\n- User copies to: `.claude\u002Fcommands\u002F[command-name].md` (when ready)\n\n---\n\n## Example Invocations\n\n### Use a Preset\n\n```\n@slash-command-factory\n\nGenerate the \u002Fresearch-content preset command\n```\n\n→ Creates content research command with all features\n\n---\n\n### Create Custom Healthcare Command\n\n```\n@slash-command-factory\n\nCreate a command that generates German PTV 10 therapy applications\n```\n\n**Skill asks**:\n- Purpose? (Generate PTV 10 applications)\n- Tools? (Read, Write, Task)\n- Agents? (Yes - health-sdk-builder related agents)\n- Output? (Files - therapy application documents)\n- Model? (Sonnet - for quality)\n\n**Result**: `\u002Fgenerate-ptv10` command ready to use\n\n---\n\n### Create Business Intelligence Command\n\n```\n@slash-command-factory\n\nBuild a command for competitive SWOT analysis\n```\n\n**Skill asks 5-7 questions** → **Generates `\u002Fswot-analysis` command** → **Validates** → **Ready to install**\n\n---\n\n## Integration with Factory Agents\n\n**Works with**:\n- factory-guide (can delegate to this skill via prompts-guide pattern)\n- Existing slash commands (\u002Fbuild, \u002Fvalidate-output, etc.)\n\n**Complements**:\n- skills-guide (builds Skills)\n- prompts-guide (builds Prompts)\n- agents-guide (builds Agents)\n- slash-command-factory (builds Commands) ← This skill\n\n**Complete ecosystem** for building all Claude Code augmentations!\n\n---\n\n## Output Validation\n\nGenerated commands are validated for:\n\n**YAML Frontmatter**:\n- Has `description` field\n- Proper YAML syntax\n- Valid frontmatter fields only\n\n**Arguments**:\n- Uses $ARGUMENTS if needed\n- Has argument-hint if $ARGUMENTS used\n- No $1, $2, $3 positional args\n\n**Tools**:\n- Valid tool names\n- Proper comma-separated format\n- Appropriate for command purpose\n\n**Organization**:\n- .md files in root\n- Folders properly separated\n- No scattered files\n\n---\n\n## Success Criteria\n\nGenerated commands should:\n- ✅ Have valid YAML frontmatter\n- ✅ Use $ARGUMENTS (never positional)\n- ✅ Work when copied to .claude\u002Fcommands\u002F\n- ✅ Execute correctly with arguments\n- ✅ Produce expected output\n- ✅ Follow organizational standards\n\n---\n\n**Version**: 1.0.0\n**Last Updated**: October 28, 2025\n**Compatible**: Claude Code (all versions with slash command support)\n\n**Build powerful custom slash commands in minutes!** ⚡\n\n","# Slash Command Factory\n\nA comprehensive system for generating production-ready Claude Code slash commands through a simple question-based workflow.\n\n---\n\n## What This Skill Does\n\nThis skill helps you create custom slash commands for Claude Code by:\n- Asking 5-7 straightforward questions about your command needs\n- Generating complete command .md files with proper YAML frontmatter\n- Providing 10 powerful preset commands for common use cases\n- Validating command format and syntax\n- Creating well-organized folder structures\n- Offering installation guidance\n\n**Output**: Complete slash commands ready to use in Claude Code\n\n---\n\n## Official Command Structure Patterns\n\nThis skill generates commands following **three official patterns** from Anthropic documentation:\n\n### Pattern A: Simple (Context → Task)\n\n**Best for**: Straightforward tasks with clear input\u002Foutput\n**Example**: Code review, file updates, simple analysis\n**Official Reference**: code-review.md\n\n**Structure**:\n```markdown\n---\nallowed-tools: Bash(git diff:*), Bash(git log:*)\ndescription: Purpose description\n---\n\n## Context\n- Current state: !`bash command`\n- Additional data: !`another command`\n\n## Your task\n[Clear instructions with numbered steps]\n[Success criteria]\n```\n\n**When to use**:\n- Simple, focused tasks\n- Quick analysis or reviews\n- Straightforward workflows\n- 1-3 bash commands for context\n\n---\n\n### Pattern B: Multi-Phase (Discovery → Analysis → Task)\n\n**Best for**: Complex discovery and documentation tasks\n**Example**: Codebase analysis, comprehensive audits, system mapping\n**Official Reference**: codebase-analysis.md\n\n**Structure**:\n```markdown\n---\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*)\ndescription: Comprehensive purpose\n---\n\n# Command Title\n\n## Phase 1: Project Discovery\n### Directory Structure\n!`find . -type d | sort`\n\n### File Count Analysis\n!`find . -type f | wc -l`\n\n## Phase 2: Detailed Analysis\n[More discovery commands]\n[File references with @]\n\n## Phase 3: Your Task\nBased on all discovered information, create:\n\n1. **Deliverable 1**\n   - Subsection\n   - Details\n\n2. **Deliverable 2**\n   - Subsection\n   - Details\n\nAt the end, write output to [filename].md\n```\n\n**When to use**:\n- Comprehensive analysis needed\n- Multiple discovery phases\n- Large amounts of context gathering\n- 10+ bash commands for data collection\n- Generate detailed documentation files\n\n---\n\n### Pattern C: Agent-Style (Role → Process → Guidelines)\n\n**Best for**: Specialized expert roles and coordination\n**Example**: Domain experts, orchestrators, specialized advisors\n**Official Reference**: openapi-expert.md\n\n**Structure**:\n```markdown\n---\nname: command-name\ndescription: |\n  Multi-line description for complex purpose\n  explaining specialized role\ncolor: yellow\n---\n\nYou are a [specialized role] focusing on [domain expertise].\n\n**Core Responsibilities:**\n\n1. **Responsibility Area 1**\n   - Specific tasks\n   - Expected outputs\n\n2. **Responsibility Area 2**\n   - Specific tasks\n   - Expected outputs\n\n**Working Process:**\n\n1. [Step 1 in workflow]\n2. [Step 2 in workflow]\n3. [Step 3 in workflow]\n\n**Important Considerations:**\n\n- [Guideline 1]\n- [Guideline 2]\n- [Constraint or best practice]\n\nWhen you encounter [scenario], [action to take].\n```\n\n**When to use**:\n- Need specialized domain expertise\n- Orchestrating complex workflows\n- Coordinating multiple sub-processes\n- Acting as expert advisor\n- Require specific procedural guidelines\n\n---\n\n## Comprehensive Naming Convention\n\n### Command File Naming Rules\n\nAll slash command files MUST follow kebab-case convention:\n\n**Format**: `[verb]-[noun].md`, `[noun]-[verb].md`, or `[domain]-[action].md`\n\n**Rules**:\n1. **Case**: Lowercase only with hyphens as separators\n2. **Length**: 2-4 words maximum\n3. **Characters**: Only `[a-z0-9-]` allowed (letters, numbers, hyphens)\n4. **Start\u002FEnd**: Must begin and end with letter or number (not hyphen)\n5. **No**: Spaces, underscores, camelCase, TitleCase, or special characters\n\n---\n\n### Conversion Algorithm\n\n**User Input** → **Command Name**\n\n```\nInput: \"Analyze customer feedback and generate insights\"\n↓\n1. Extract action: \"analyze\"\n2. Extract target: \"feedback\"\n3. Combine: \"analyze-feedback\"\n4. Validate: Matches [a-z0-9-]+ pattern ✓\n5. Output: analyze-feedback.md\n```\n\n**More Examples**:\n- \"Review pull requests\" → `pr-review.md` or `review-pr.md`\n- \"Generate API documentation\" → `api-document.md` or `document-api.md`\n- \"Update README files\" → `update-readme.md` or `readme-update.md`\n- \"Audit security compliance\" → `security-audit.md` or `compliance-audit.md`\n- \"Research market trends\" → `research-market.md` or `market-research.md`\n- \"Analyze code quality\" → `code-analyze.md` or `analyze-code.md`\n\n---\n\n### Official Examples (From Anthropic Docs)\n\n**Correct**:\n- ✅ `code-review.md` (verb-noun)\n- ✅ `codebase-analysis.md` (noun-noun compound)\n- ✅ `update-claude-md.md` (verb-noun-qualifier)\n- ✅ `openapi-expert.md` (domain-role)\n\n**Incorrect**:\n- ❌ `code_review.md` (snake_case - wrong)\n- ❌ `CodeReview.md` (PascalCase - wrong)\n- ❌ `codeReview.md` (camelCase - wrong)\n- ❌ `review.md` (too vague - needs target)\n- ❌ `analyze-customer-feedback-data.md` (too long - >4 words)\n\n---\n\n## Bash Permission Patterns\n\n### Critical Rule: No Wildcards\n\n**❌ NEVER ALLOWED**:\n```yaml\nallowed-tools: Bash\n```\nThis wildcard permission is **prohibited** per official Anthropic patterns.\n\n**✅ ALWAYS REQUIRED**:\n```yaml\nallowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*)\n```\nMust specify **exact commands** with wildcards only for subcommands.\n\n---\n\n### Official Permission Patterns\n\nBased on Anthropic's documented examples:\n\n**Git Operations** (code-review, update-docs):\n```yaml\nallowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git branch:*), Bash(git add:*), Bash(git commit:*)\n```\n\n**File Discovery** (codebase-analysis):\n```yaml\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(du:*)\n```\n\n**Content Analysis** (comprehensive discovery):\n```yaml\nallowed-tools: Bash(grep:*), Bash(wc:*), Bash(head:*), Bash(tail:*), Bash(cat:*)\n```\n\n**Data Processing** (custom analysis):\n```yaml\nallowed-tools: Bash(awk:*), Bash(sed:*), Bash(sort:*), Bash(uniq:*)\n```\n\n**Combined Patterns** (multi-phase commands):\n```yaml\nallowed-tools: Bash(find:*), Bash(tree:*), Bash(ls:*), Bash(grep:*), Bash(wc:*), Bash(du:*), Bash(head:*), Bash(tail:*), Bash(cat:*), Bash(touch:*)\n```\n\n---\n\n### Permission Selection Guide\n\n| Command Type | Bash Permissions | Example Commands |\n|--------------|------------------|------------------|\n| **Git Commands** | `git status, git diff, git log, git branch` | code-review, commit-assist |\n| **Discovery** | `find, tree, ls, du` | codebase-analyze, structure-map |\n| **Analysis** | `grep, wc, head, tail, cat` | search-code, count-lines |\n| **Update** | `git diff, find, grep` | update-docs, sync-config |\n| **Data Processing** | `awk, sed, sort, uniq` | parse-data, format-output |\n| **Comprehensive** | All of the above | full-audit, system-analyze |\n\n---\n\n## Two Paths to Generate Commands\n\n### Path 1: Quick-Start Presets (30 seconds)\n\nChoose from 10 powerful preset commands:\n\n**Business & Research**:\n1. **\u002Fresearch-business** - Comprehensive market research and competitive analysis\n2. **\u002Fresearch-content** - Multi-platform content trend analysis and SEO strategy\n\n**Healthcare & Compliance**:\n3. **\u002Fmedical-translate** - Translate medical terminology to 8th-10th grade (German\u002FEnglish) \n4. **\u002Fcompliance-audit** - HIPAA\u002FGDPR\u002FDSGVO compliance validation\n\n**Development & Integration**:\n5. **\u002Fapi-build** - Generate complete API integration code with tests\n6. **\u002Ftest-auto** - Auto-generate comprehensive test suites\n\n**Documentation & Knowledge**:\n7. **\u002Fdocs-generate** - Automated documentation creation\n8. **\u002Fknowledge-mine** - Extract and structure insights from documents\n\n**Workflow & Productivity**:\n9. **\u002Fworkflow-analyze** - Analyze and optimize business processes\n10. **\u002Fbatch-agents** - Launch and coordinate multiple agents for complex tasks\n\n### Path 2: Custom Command (5-7 Questions)\n\nCreate a completely custom command for your specific needs.\n\n---\n\n## Question Flow (Custom Path)\n\n### Question 1: Command Purpose\n\n\"What should this slash command do?\n\nBe specific about its purpose and when you'll use it.\n\nExamples:\n- 'Analyze customer feedback and generate actionable insights'\n- 'Generate HIPAA-compliant API documentation'\n- 'Research market trends and create content strategy'\n- 'Extract key insights from research papers'\n\nYour command's purpose: ___\"\n\n---\n\n### Question 2: Arguments (Auto-Determined)\n\nThe skill automatically determines if your command needs arguments based on the purpose.\n\n**If arguments are needed**, they will use `$ARGUMENTS` format:\n- User types: `\u002Fyour-command argument1 argument2`\n- Command receives: `$ARGUMENTS` = \"argument1 argument2\"\n\n**Examples**:\n- `\u002Fresearch-business \"Tesla\" \"EV market\"` → $ARGUMENTS = \"Tesla EV market\"\n- `\u002Fmedical-translate \"Myokardinfarkt\" \"de\"` → $ARGUMENTS = \"Myokardinfarkt de\"\n\n**No user input needed** - skill decides intelligently.\n\n---\n\n### Question 3: Which Tools?\n\n\"Which Claude Code tools should this command use?\n\nAvailable tools:\n- **Read** - Read files\n- **Write** - Create files\n- **Edit** - Modify files\n- **Bash** - Execute shell commands (MUST specify exact commands)\n- **Grep** - Search code\n- **Glob** - Find files by pattern\n- **Task** - Launch agents\n\n**CRITICAL**: For Bash, you MUST specify exact commands, not wildcards.\n\n**Bash Examples**:\n- ✅ Bash(git status:*), Bash(git diff:*), Bash(git log:*)\n- ✅ Bash(find:*), Bash(tree:*), Bash(ls:*)\n- ✅ Bash(grep:*), Bash(wc:*), Bash(head:*)\n- ❌ Bash (wildcard not allowed per official patterns)\n\n**Tool Combination Examples**:\n- Git command: Read, Bash(git status:*), Bash(git diff:*)\n- Code generator: Read, Write, Edit\n- Discovery command: Bash(find:*), Bash(tree:*), Bash(grep:*)\n- Analysis command: Read, Grep, Task (launch agents)\n\nYour tools (comma-separated): ___\"\n\n---\n\n### Question 4: Agent Integration\n\n\"Does this command need to launch agents for specialized tasks?\n\nExamples of when to use agents:\n- Complex analysis (launch rr-architect, rr-security)\n- Implementation tasks (launch rr-frontend, rr-backend)\n- Quality checks (launch rr-qa, rr-test-runner)\n\nOptions:\n1. **No agents** - Command handles everything itself\n2. **Launch agents** - Delegate to specialized agents\n\nYour choice (1 or 2): ___\"\n\nIf \"2\", ask: \"Which agents should it launch? ___\"\n\n---\n\n### Question 5: Output Type\n\n\"What type of output should this command produce?\n\n1. **Analysis** - Research report, insights, recommendations\n2. **Files** - Generated code, documentation, configs\n3. **Action** - Execute tasks, run workflows, deploy\n4. **Report** - Structured report with findings and next steps\n\nYour choice (1, 2, 3, or 4): ___\"\n\n---\n\n### Question 6: Model Preference (Optional)\n\n\"Which Claude model should this command use?\n\n1. **Default** - Inherit from main conversation (recommended)\n2. **Sonnet** - Best for complex tasks\n3. **Haiku** - Fastest, cheapest (for simple commands)\n4. **Opus** - Maximum capability (for critical tasks)\n\nYour choice (1, 2, 3, or 4) or press Enter for default: ___\"\n\n---\n\n### Question 7: Additional Features (Optional)\n\n\"Any special features?\n\nOptional features:\n- **Bash execution** - Run shell commands and include output (!`command`)\n- **File references** - Include file contents (@file.txt)\n- **Context gathering** - Read project files for context\n\nFeatures you need (comma-separated) or press Enter to skip: ___\"\n\n---\n\n## Generation Process\n\nAfter collecting answers:\n\n1. **Generate YAML Frontmatter**:\n```yaml\n---\ndescription: [From command purpose]\nargument-hint: [If $ARGUMENTS needed]\nallowed-tools: [From tool selection]\nmodel: [If specified]\n---\n```\n\n2. **Generate Command Body**:\n```markdown\n[Purpose-specific instructions]\n\n[If uses agents]:\n1. **Launch [agent-name]** with [specific task]\n2. Coordinate workflow\n3. Validate results\n\n[If uses bash]:\n- Context: !`bash command`\n\n[If uses file refs]:\n- Review: @file.txt\n\nSuccess Criteria: [Based on output type]\n```\n\n3. **Create Folder Structure**:\n```\ngenerated-commands\u002F[command-name]\u002F\n├── [command-name].md    # Command file (ROOT)\n├── README.md            # Installation guide (ROOT)\n├── TEST_EXAMPLES.md     # Testing examples (ROOT)\n└── [folders if needed]  # standards\u002F, examples\u002F, scripts\u002F\n```\n\n4. **Validate Format**:\n- ✅ YAML frontmatter valid\n- ✅ $ARGUMENTS syntax correct (if used)\n- ✅ allowed-tools format proper\n- ✅ Folder organization clean\n\n5. **Provide Installation Instructions**:\n```\nYour command is ready!\n\nOutput location: generated-commands\u002F[command-name]\u002F\n\nTo install:\n1. Copy the command file:\n   cp generated-commands\u002F[command-name]\u002F[command-name].md .claude\u002Fcommands\u002F\n\n2. Restart Claude Code (if already running)\n\n3. Test:\n   \u002F[command-name] [arguments]\n```\n\n---\n\n## Preset Command Details\n\n### 1. \u002Fresearch-business\n\n**Purpose**: Comprehensive business and market research\n\n**Arguments**: `$ARGUMENTS` (company or market to research)\n\n**YAML**:\n```yaml\n---\ndescription: Comprehensive business and market research with competitor analysis\nargument-hint: [company\u002Fmarket] [industry]\nallowed-tools: Read, Bash, Grep\n---\n```\n\n**What it does**:\n- Market size and trends analysis\n- Competitor SWOT analysis\n- Opportunity identification\n- Industry landscape overview\n- Strategic recommendations\n\n---\n\n### 2. \u002Fresearch-content\n\n**Purpose**: Multi-platform content trend analysis\n\n**Arguments**: `$ARGUMENTS` (topic to research)\n\n**YAML**:\n```yaml\n---\ndescription: Multi-platform content trend analysis for data-driven content strategy\nargument-hint: [topic] [platforms]\nallowed-tools: Read, Bash\n---\n```\n\n**What it does**:\n- Analyze trends across Google, Reddit, YouTube, Medium, LinkedIn, X\n- User intent analysis (informational, commercial, transactional)\n- Content gap identification\n- SEO-optimized outline generation\n- Platform-specific publishing strategies\n\n---\n\n### 3. \u002Fmedical-translate\n\n**Purpose**: Translate medical terminology to patient-friendly language\n\n**Arguments**: `$ARGUMENTS` (medical term and language)\n\n**YAML**:\n```yaml\n---\ndescription: Translate medical terminology to 8th-10th grade reading level (German\u002FEnglish)\nargument-hint: [medical-term] [de|en]\nallowed-tools: Read\n---\n```\n\n**What it does**:\n- Translate complex medical terms\n- Simplify to 8th-10th grade reading level\n- Validate with Flesch-Kincaid (EN) or Wiener Sachtextformel (DE)\n- Preserve clinical accuracy\n- Provide patient-friendly explanations\n\n---\n\n### 4. \u002Fcompliance-audit\n\n**Purpose**: Check code for regulatory compliance\n\n**Arguments**: `$ARGUMENTS` (path and compliance standard)\n\n**YAML**:\n```yaml\n---\ndescription: Audit code for HIPAA\u002FGDPR\u002FDSGVO compliance requirements\nargument-hint: [code-path] [hipaa|gdpr|dsgvo|all]\nallowed-tools: Read, Grep, Task\n---\n```\n\n**What it does**:\n- Scan for PHI\u002FPII handling\n- Check encryption requirements\n- Verify audit logging\n- Validate data subject rights\n- Generate compliance report\n\n---\n\n### 5. \u002Fapi-build\n\n**Purpose**: Generate complete API integration code\n\n**Arguments**: `$ARGUMENTS` (API name and endpoints)\n\n**YAML**:\n```yaml\n---\ndescription: Generate complete API client with error handling and tests\nargument-hint: [api-name] [endpoints]\nallowed-tools: Read, Write, Edit, Bash, Task\n---\n```\n\n**What it does**:\n- Generate API client classes\n- Add error handling and retries\n- Create authentication logic\n- Generate unit and integration tests\n- Add usage documentation\n\n---\n\n### 6. \u002Ftest-auto\n\n**Purpose**: Auto-generate comprehensive test suites\n\n**Arguments**: `$ARGUMENTS` (file path and test type)\n\n**YAML**:\n```yaml\n---\ndescription: Auto-generate comprehensive test suite with coverage analysis\nargument-hint: [file-path] [unit|integration|e2e]\nallowed-tools: Read, Write, Bash\n---\n```\n\n**What it does**:\n- Analyze code to test\n- Generate test cases (happy path, edge cases, errors)\n- Add test fixtures and mocks\n- Calculate coverage\n- Provide testing documentation\n\n---\n\n### 7. \u002Fdocs-generate\n\n**Purpose**: Automated documentation generation\n\n**Arguments**: `$ARGUMENTS` (code path and doc type)\n\n**YAML**:\n```yaml\n---\ndescription: Auto-generate documentation from code (API docs, README, architecture)\nargument-hint: [code-path] [api|readme|architecture|all]\nallowed-tools: Read, Write, Grep\n---\n```\n\n**What it does**:\n- Extract code structure and functions\n- Generate API documentation\n- Create README with usage examples\n- Build architecture diagrams (Mermaid)\n- Add code examples\n\n---\n\n### 8. \u002Fknowledge-mine\n\n**Purpose**: Extract structured insights from documents\n\n**Arguments**: `$ARGUMENTS` (document path and output format)\n\n**YAML**:\n```yaml\n---\ndescription: Extract and structure knowledge from documents into actionable insights\nargument-hint: [doc-path] [faq|summary|kb|all]\nallowed-tools: Read, Grep\n---\n```\n\n**What it does**:\n- Read and analyze documents\n- Extract key insights\n- Generate FAQs\n- Create knowledge base articles\n- Summarize findings\n\n---\n\n### 9. \u002Fworkflow-analyze\n\n**Purpose**: Analyze and optimize business workflows\n\n**Arguments**: `$ARGUMENTS` (workflow description)\n\n**YAML**:\n```yaml\n---\ndescription: Analyze workflows and provide optimization recommendations\nargument-hint: [workflow-description]\nallowed-tools: Read, Task\n---\n```\n\n**What it does**:\n- Map current workflow\n- Identify bottlenecks\n- Suggest automation opportunities\n- Calculate efficiency gains\n- Create implementation roadmap\n\n---\n\n### 10. \u002Fbatch-agents\n\n**Purpose**: Launch multiple coordinated agents\n\n**Arguments**: `$ARGUMENTS` (agent names and task)\n\n**YAML**:\n```yaml\n---\ndescription: Launch and coordinate multiple agents for complex tasks\nargument-hint: [agent-names] [task-description]\nallowed-tools: Task\n---\n```\n\n**What it does**:\n- Parse agent list\n- Launch agents in parallel (if safe) or sequential\n- Coordinate outputs\n- Integrate results\n- Provide comprehensive summary\n\n---\n\n## Output Structure\n\nCommands are generated in your project's root directory:\n\n```\n[your-project]\u002F\n└── generated-commands\u002F\n    └── [command-name]\u002F\n        ├── [command-name].md      # Command file (ROOT level)\n        ├── README.md              # Installation guide (ROOT level)\n        ├── TEST_EXAMPLES.md       # Testing guide (ROOT level - if applicable)\n        │\n        ├── standards\u002F             # Only if command has standards\n        ├── examples\u002F              # Only if command has examples\n        └── scripts\u002F               # Only if command has helper scripts\n```\n\n**Organization Rules**:\n- All .md files in ROOT directory\n- Supporting folders separate (standards\u002F, examples\u002F, scripts\u002F)\n- No mixing of different types in same folder\n- Clean, hierarchical structure\n\n---\n\n## Installation\n\n**After generation**:\n\n1. **Review output**:\n   ```bash\n   ls generated-commands\u002F[command-name]\u002F\n   ```\n\n2. **Copy to Claude Code** (when ready):\n   ```bash\n   # Project-level (this project only)\n   cp generated-commands\u002F[command-name]\u002F[command-name].md .claude\u002Fcommands\u002F\n\n   # User-level (all projects)\n   cp generated-commands\u002F[command-name]\u002F[command-name].md ~\u002F.claude\u002Fcommands\u002F\n   ```\n\n3. **Restart Claude Code** (if running)\n\n4. **Test command**:\n   ```bash\n   \u002F[command-name] [arguments]\n   ```\n\n---\n\n## Usage Examples\n\n### Generate a Preset Command\n\n```\n@slash-command-factory\n\nUse the \u002Fresearch-business preset\n```\n\n**Output**: Complete business research command ready to install\n\n---\n\n### Generate a Custom Command\n\n```\n@slash-command-factory\n\nCreate a custom command for analyzing customer feedback and generating product insights\n```\n\n**Skill asks 5-7 questions** → **Generates complete command** → **Validates format** → **Provides installation steps**\n\n---\n\n## Command Format (What Gets Generated)\n\n**Example generated command** (`my-command.md`):\n\n```markdown\n---\ndescription: Brief description of what the command does\nargument-hint: [arg1] [arg2]\nallowed-tools: Read, Write, Bash\nmodel: claude-3-5-sonnet-20241022\n---\n\n# Command Instructions\n\nDo [task] with \"$ARGUMENTS\":\n\n1. **Step 1**: First action\n2. **Step 2**: Second action\n3. **Step 3**: Generate output\n\n**Success Criteria**:\n- Criterion 1\n- Criterion 2\n- Criterion 3\n```\n\n---\n\n## Validation\n\nEvery generated command is automatically validated for:\n- ✅ Valid YAML frontmatter (proper syntax, required fields)\n- ✅ Correct argument format ($ARGUMENTS, not $1 $2 $3)\n- ✅ allowed-tools syntax (comma-separated string)\n- ✅ Clean folder organization (if folders used)\n- ✅ No placeholder text\n\n**If validation fails**, you'll get specific fix instructions.\n\n---\n\n## Best Practices\n\n**For Command Design**:\n- Keep commands focused (one clear purpose)\n- Use descriptive names (kebab-case for files)\n- Document expected arguments clearly\n- Include success criteria\n- Add examples in TEST_EXAMPLES.md\n\n**For Tool Selection**:\n- Read: For analyzing files\n- Write\u002FEdit: For generating\u002Fmodifying files\n- Bash: For system commands, web research\n- Task: For launching agents\n- Grep\u002FGlob: For searching code\n\n**For Agent Integration**:\n- Use Task tool to launch agents\n- Specify which agents clearly\n- Coordinate outputs\n- Document agent roles\n\n---\n\n## Important Notes\n\n**Arguments**:\n- ✅ Always use `$ARGUMENTS` (all arguments as one string)\n- ❌ Never use `$1`, `$2`, `$3` (positional - not used by this factory)\n\n**Folder Organization**:\n- ✅ All .md files in command root directory\n- ✅ Supporting folders separate (standards\u002F, examples\u002F, scripts\u002F)\n- ✅ No mixing of different types\n\n**Output Location**:\n- Commands generate to: `.\u002Fgenerated-commands\u002F[command-name]\u002F`\n- User copies to: `.claude\u002Fcommands\u002F[command-name].md` (when ready)\n\n---\n\n## Example Invocations\n\n### Use a Preset\n\n```\n@slash-command-factory\n\nGenerate the \u002Fresearch-content preset command\n```\n\n→ Creates content research command with all features\n\n---\n\n### Create Custom Healthcare Command\n\n```\n@slash-command-factory\n\nCreate a command that generates German PTV 10 therapy applications\n```\n\n**Skill asks**:\n- Purpose? (Generate PTV 10 applications)\n- Tools? (Read, Write, Task)\n- Agents? (Yes - health-sdk-builder related agents)\n- Output? (Files - therapy application documents)\n- Model? (Sonnet - for quality)\n\n**Result**: `\u002Fgenerate-ptv10` command ready to use\n\n---\n\n### Create Business Intelligence Command\n\n```\n@slash-command-factory\n\nBuild a command for competitive SWOT analysis\n```\n\n**Skill asks 5-7 questions** → **Generates `\u002Fswot-analysis` command** → **Validates** → **Ready to install**\n\n---\n\n## Integration with Factory Agents\n\n**Works with**:\n- factory-guide (can delegate to this skill via prompts-guide pattern)\n- Existing slash commands (\u002Fbuild, \u002Fvalidate-output, etc.)\n\n**Complements**:\n- skills-guide (builds Skills)\n- prompts-guide (builds Prompts)\n- agents-guide (builds Agents)\n- slash-command-factory (builds Commands) ← This skill\n\n**Complete ecosystem** for building all Claude Code augmentations!\n\n---\n\n## Output Validation\n\nGenerated commands are validated for:\n\n**YAML Frontmatter**:\n- Has `description` field\n- Proper YAML syntax\n- Valid frontmatter fields only\n\n**Arguments**:\n- Uses $ARGUMENTS if needed\n- Has argument-hint if $ARGUMENTS used\n- No $1, $2, $3 positional args\n\n**Tools**:\n- Valid tool names\n- Proper comma-separated format\n- Appropriate for command purpose\n\n**Organization**:\n- .md files in root\n- Folders properly separated\n- No scattered files\n\n---\n\n## Success Criteria\n\nGenerated commands should:\n- ✅ Have valid YAML frontmatter\n- ✅ Use $ARGUMENTS (never positional)\n- ✅ Work when copied to .claude\u002Fcommands\u002F\n- ✅ Execute correctly with arguments\n- ✅ Produce expected output\n- ✅ Follow organizational standards\n\n---\n\n**Version**: 1.0.0\n**Last Updated**: October 28, 2025\n**Compatible**: Claude Code (all versions with slash command support)\n\n**Build powerful custom slash commands in minutes!** ⚡\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Fslash-command-factory",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill slash-command-factory",{"tool":75,"command":76},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill slash-command-factory",{"tool":78,"command":79},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill slash-command-factory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Falirezarezvani\u002Fclaude-code-skill-factory\u002Fslash-command-factory\u002FSKILL.md",true,[],[84,94,104,113,119,126],{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":90,"publishedAt":55},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[89],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[91,92,93],"model","model hierarchy","model hierarchy skill",{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":100,"publishedAt":55},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[99],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[101,102,103],"MCP","zoom","zoom mcp",{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":55},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[110,111,112,102],"sdk","zoom apps sdk","apps",{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":55},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[115],{"skillNo":120,"name":121,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":55},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[124],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[121],{"skillNo":127,"name":128,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":55},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[128]]