command-creator

Generate Claude Code slash command templates with frontmatter and dynamic arguments.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/hungson175/shared-claude-config --skill command-creator-hungson175
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-creator
Source: https://github.com/hungson175/shared-claude-config/tree/main/skills/command-creator
Command: npx skills add https://github.com/hungson175/shared-claude-config --skill command-creator-hungson175

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams and individuals translate user requests into ready-to-use Claude Code slash commands, reducing boilerplate and ensuring consistent command structures.

Core Features & Use Cases

  • Templates: Generate command Markdown files with frontmatter fields and structured instructions.
  • Locations & Scopes: Produce commands for project, personal, or plugin contexts (e.g., .claude/commands/, ~/.claude/commands/, or plugin-name/commands/).
  • Dynamic Arguments & References: Include dynamic arguments ($ARGUMENTS, $1, $2) and file references with @syntax.
  • Best Practices: Enforces clear naming, argument documentation, and controlled tool usage.

Quick Start

Create a new command template for /build in your project by adding .claude/commands/build.md with proper frontmatter and a minimal body.

Frequently Asked Questions about command-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom Claude Code slash commands for my project?

To create Claude Code slash commands, generate Markdown files with frontmatter fields and structured instructions inside the .claude/commands/ directory. You can translate user intents into ready-to-use templates with consistent naming and documented arguments.

What is the difference between project, personal, and plugin command scopes in Claude Code?

Claude Code command scopes determine file placement: project commands go in .claude/commands/, personal commands in ~/.claude/commands/, and plugin commands in plugin-name/commands/. Each scope dictates where your Markdown templates are stored and accessed.

How do I use dynamic arguments and file references in Claude Code command templates?

Dynamic arguments in Claude Code command templates utilize $ARGUMENTS, $1, and $2 syntax for variable input, while file references use @syntax. This enables flexible Bash-integrated workflows and parameterized instructions within your Markdown files.

Can I integrate Bash workflows into my Claude Code command templates?

Yes, Claude Code command templates support Bash-integrated workflows. You can embed controlled tool usage and shell commands within the Markdown body, allowing your commands to execute scripts and automate terminal tasks safely.

What are the best practices for structuring Claude Code command frontmatter?

Best practices for Claude Code command frontmatter include enforcing clear naming conventions, documenting all arguments explicitly, and ensuring controlled tool usage. This reduces boilerplate and maintains consistent command structures across templates.

Do I need a specific directory structure to add a custom slash command in Claude Code?

Yes, adding a custom slash command requires placing a Markdown file in the appropriate commands directory, such as .claude/commands/ for project scope. The file must contain proper frontmatter and a minimal body to function correctly.