command-development

Create Claude Code slash commands with YAML frontmatter and Bash execution.

28|5|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/thevibeworks/claude-code-docs --skill command-development-thevibeworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-development
Source: https://github.com/thevibeworks/claude-code-docs/tree/main/content/github/claude-plugins-official/plugins/plugin-dev/skills/command-development
Command: npx skills add https://github.com/thevibeworks/claude-code-docs --skill command-development-thevibeworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

You need to create slash commands that work reliably in Claude Code, but the correct structure, YAML frontmatter options, argument handling, and execution patterns are unclear.

Core Features & Use Cases

  • Slash command authoring: Define commands as Markdown prompts with correct instruction framing and placement.
  • YAML frontmatter configuration: Use fields like description, allowed-tools, model, argument-hint, and disable-model-invocation to control discovery and behavior.
  • Dynamic inputs & execution: Inject arguments with $ARGUMENTS and $1/$2, include file contents with @ syntax, and gather context by running Bash with !....
  • Plugin-aware command patterns: Use ${CLAUDE_PLUGIN_ROOT} for portable paths and design commands that integrate with plugin scripts, resources, agents, and other skills.
  • Validation and troubleshooting: Apply best practices for input/resource validation, error handling, and diagnosing missing commands or failing arguments.

Quick Start

Create a new command file that includes a YAML frontmatter description and an argument-hint, then write Claude instructions that use $1 for the user-provided value and (optionally) use !... for repository context.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I create Claude Code slash commands with dynamic arguments?

You create Claude Code slash commands by writing Markdown prompt files with YAML frontmatter, using $ARGUMENTS or $1/$2 syntax for dynamic argument substitution, and defining an argument-hint to guide users during input.

What YAML frontmatter fields are available for Claude Code commands?

Claude Code command YAML frontmatter supports fields like description for discovery, allowed-tools for tool restriction, model, argument-hint for input guidance, and disable-model-invocation to control command behavior.

How do I include file contents and run Bash commands inside a Claude Code prompt?

You include file contents using the @ path syntax and gather repository context by executing Bash commands directly within the prompt using the !`...` execution pattern for safe command execution.

Can I configure plugin-scoped slash commands using portable paths?

Yes, you configure plugin-scoped commands by using the ${CLAUDE_PLUGIN_ROOT} variable for portable paths, allowing your commands to integrate with plugin scripts, resources, agents, and other skills reliably.

Why is my Claude Code slash command not showing up in /help?

Slash commands require proper YAML frontmatter configuration with a description field for discovery, and missing commands or failing arguments often result from incorrect instruction framing, invalid paths, or lacking input validation.

What is the best way to validate inputs and handle errors in Claude Code commands?

The best way to validate inputs in Claude Code commands is applying best practices for input and resource validation, robust error handling, and troubleshooting patterns to diagnose missing commands or failing arguments.