create-command

Create Claude Code slash commands with YAML frontmatter and metadata.

14|1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/jpoutrin/product-forge --skill create-command-jpoutrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-command
Source: https://github.com/jpoutrin/product-forge/tree/main/plugins/claude-code-dev/skills/create-command
Command: npx skills add https://github.com/jpoutrin/product-forge --skill create-command-jpoutrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a template for adding new Claude Code slash commands with YAML frontmatter and advanced features.

Core Features & Use Cases

  • Command file format with description, argument hints, allowed-tools
  • Advanced features: child placeholders, code references, and execution instructions

Quick Start

Create a markdown file under commands/ with the correct YAML frontmatter to implement a new slash command.

Frequently Asked Questions about create-command

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

FAQPage Schema
How do I create a custom slash command in Claude Code?

Create a markdown file in `.claude/commands/` or `~/.claude/commands/` with YAML frontmatter defining description, argument-hint, allowed-tools, and model settings. The frontmatter structure specifies command behavior, and the markdown body contains the command logic with support for placeholder arguments like $ARGUMENTS, $1, and $2.

What YAML fields do I need to define in a slash command file?

Required YAML frontmatter fields include description, argument-hint, allowed-tools, model, and disable-model-invocation. These fields control command metadata, accepted arguments, tool permissions, model selection, and execution behavior for your custom Claude Code command.

Can I use argument placeholders in Claude Code slash commands?

Yes, slash commands support placeholder arguments including $ARGUMENTS for all passed arguments, $1 and $2 for individual positional arguments, and Bash pre-run commands. These placeholders enable dynamic command behavior based on user input and file references.

Where do I store slash commands for project-wide versus user-wide use?

Store project-scoped commands in `.claude/commands/` or `plugins/<plugin>/commands/` within your project directory. Store user-scoped commands in `~/.claude/commands/` for access across all Claude Code sessions on your machine.

What automation tasks can I handle with custom slash commands?

Custom slash commands automate CLI workflows by executing Bash pre-run commands, referencing external files, and passing arguments through placeholders. They support namespacing and tool restrictions, enabling project-specific automation without modifying Claude Code's core behavior.

Do I need coding experience to define slash command metadata?

No, slash commands use declarative YAML frontmatter and straightforward markdown syntax. Understanding basic YAML key-value pairs and placeholder syntax is sufficient to create functional commands without deep programming knowledge.