command-development

To create a Claude Code slash command, you write a Markdown file with YAML frontmatter containing a name and description, followed by a prompt. This structured frontmatter establishes consistent command organization and namespacing for plugin-based automation.

Dynamic arguments in slash commands are structured using $ARGUMENTS, positional variables like $1, and @path syntax for file references. This allows interactive flows to accept dynamic inputs and execute Bash patterns within the command template.

Command namespacing organizes plugin and project commands by applying clear naming conventions within the YAML frontmatter. This structured organization prevents naming collisions and coordinates command execution across different plugin resources.

Yes, custom slash commands support integration and validation patterns by coordinating hooks, agents, and skills. This enables reliable automation workflows that validate command execution and extend functionality across multi-file references.

The allowed-tools and model fields are optional frontmatter properties for slash commands. Including them provides frontmatter pattern guidance to control tool access and model selection, ensuring commands execute with the appropriate permissions.

Slash command file references fail when the @path syntax is incorrectly structured or the referenced file is missing. Ensure dynamic arguments and file references follow the established template patterns and Bash execution syntax for proper validation.