command-development

To create a Claude Code slash command, define a Markdown file under the commands directory with proper YAML frontmatter specifying description, allowed-tools, model, and argument hints. Validate the structure through in-session testing to ensure consistent behavior.

The best way to structure dynamic arguments and file references in slash commands is by using a standardized frontmatter-driven blueprint. This approach supports flexible user input and content sourcing, allowing commands to dynamically adapt based on provided parameters and referenced resources.

Yes, you can execute bash scripts within Claude Code command workflows. Bash execution allows commands to gather contextual data and perform deterministic actions, enabling multi-step workflows that integrate system-level operations with dynamic command parameters.

You integrate plugins into multi-step command workflows using the CLAUDE_PLUGIN_ROOT environment variable. This enables access to agents, skills, templates, and hooks, allowing you to build complex multi-component workflows that extend standard slash command functionality.

Yes, the framework supports marketplace readiness and testing by enforcing YAML frontmatter validation and providing guidance for clear command organization. It includes best practices for error handling and testing patterns to ensure commands are robust before deployment.

You should use namespace-based organization for Claude Code commands when managing a large collection of workflows. This structure, alongside flat organization, helps maintain clear command separation and is recommended for documentation and marketplace readiness.