creating-commands

Custom commands use YAML frontmatter to define metadata like description, allowed-tools, argument-hint, and model settings. Structure your command with frontmatter fields at the top, then add the workflow logic and example invocations in the body to guide Claude's execution.

Use $ARGUMENTS for all inputs or positional patterns ($1, $2, $3) for specific parameters. Argument patterns let you pass user input precisely into your command logic, ensuring deterministic automation and safe parameter handling.

Bash integration uses the ! prefix for pre-execution scripts, and the @ prefix loads files as context. Together they enable deterministic automation by executing Bash before Claude acts and injecting file content into prompts for context-aware command execution.

Yes, Claude Code supports project-level, user-level, and grouped command patterns. You can craft reusable commands scoped to teams or projects, with structured YAML frontmatter and argument patterns that enforce best practices and security considerations across your workflow.

Configure allowed-tools in frontmatter to restrict which tools Claude can invoke, use argument patterns to validate user input, and avoid disable-model-invocation unless necessary. These guardrails prevent unsafe tool access and ensure commands remain predictable and secure.

Verify YAML frontmatter syntax is valid, confirm argument patterns ($1, $2, $ARGUMENTS) match your workflow, check that file references (@) point to correct paths, and review allowed-tools settings. Structured debugging of these components resolves most command invocation failures.