slash-command-design

Design commands as thin wrappers that parse arguments and delegate complex logic to specialized agents. This separation keeps commands simple, robust, and reusable while letting agents handle the heavy lifting of your automation workflow.

Commands are entry points that handle user input and invoke agents; agents orchestrate complex workflows; skills package reusable guidance. Choose the right component type based on whether you need a direct trigger, workflow coordination, or shared knowledge across multiple automations.

Frontmatter fields define command metadata and behavior; arguments become substitution patterns passed to agents. Follow the box-factory-architecture framework to ensure proper argument handling, tool usage, and isolation for reliable automation execution.

Avoid embedding logic in commands; use the delegation pattern instead. Commands work best as lightweight wrappers that invoke agents, preventing design pitfalls and maximizing reusability across your automation ecosystem.

Common pitfalls include embedding too much logic in the command itself, poor argument handling, and misaligned component choices. Adhere to best practices for frontmatter, leverage the command-versus-agent decision framework, and use quality checklists to ensure your command is actionable and discoverable.

Slash commands automate repetitive tasks by triggering agents within Claude Code's developer environment. They standardize component choice and enforce best practices, ensuring your automation integrates cleanly with AI workflows and aligns with official documentation.