creating-commands

To create structured slash commands, you define a command file using YAML frontmatter and a structured XML body. This enforces a consistent format with objective, process, success_criteria, and optional context sections, reducing human error and enabling reusable templates.

You can add dynamic context and file references to slash commands by utilizing the provided templates and patterns within the XML command body. This allows commands to dynamically load state and reference specific files during execution for repeatable, safety-checked prompts.

Yes, you can apply selective tool restrictions and define optional arguments within the YAML frontmatter. This ensures your custom slash commands operate with safety-checked prompts and controlled execution environments for targeted team workflows.

The best way to standardize slash commands across teams is to use a defined XML body and YAML frontmatter structure. Supporting both project-scoped and personal command directories facilitates collaboration and ensures consistent command patterns across projects.

You need to use XML prompts instead of plain markdown when your commands require strict structural sections like objective, process, and success_criteria. This structured approach standardizes command creation, enables dynamic state loading, and ensures repeatable safety-checked prompt execution.