slash-command-creator

Slash commands automate frequently-used prompts in Claude Code. Create custom commands by generating Markdown files with YAML frontmatter specifying command name, description, and prompt body. Use the init_command.py script to scaffold new commands with consistent structure and naming conventions.

Project-level commands are shared across your team's workspace, while personal commands remain private to your account. Both use the same Markdown file format with YAML frontmatter. Specify scope during command initialization to determine where the command file is stored and who can access it.

Yes. Beyond the required name and description, you can configure allowed-tools to restrict which tools the command invokes, set argument-hint for user guidance, specify a model, or disable model invocation entirely. These optional fields let you fine-tune automation for specific workflows.

Namespaces are optional and help organize commands logically within project or personal scope. You can structure related commands under a namespace prefix to reduce command-list clutter and improve discoverability, but flat organization works for smaller command sets.

Slash commands are Markdown files with YAML frontmatter containing metadata like name, description, and optional fields. File location depends on scope: project commands live in the shared workspace directory, personal commands in your private CLI config folder, respecting namespace subdirectories if used.

Yes, through the allowed-tools frontmatter field. You can restrict which Claude Code tools a command has access to, enabling secure automation of prompts that need specific capabilities like terminal execution, file editing, or web requests without exposing unnecessary functionality.