Where should I store my custom commands?

Personal commands should be stored in ~/.claude/commands/, while shared project commands go in .claude/commands/ within your repository.

What is the difference between $ARGUMENTS and $1?

$ARGUMENTS captures the entire user input as one string, while $1, $2, etc., capture specific space-separated parameters for more structured commands.

What is a Claude Code slash command?

It is a markdown-based prompt template stored in a specific directory that allows users to trigger complex AI tasks using a simple forward-slash prefix in the Claude Code CLI.

Can I run shell scripts inside a slash command?

Yes, you can use the [execute: command] syntax provided you define the necessary permissions in the 'allowed-tools' section of the command's YAML frontmatter.

Claude Code Slash Command Builder

Name: Claude Code Slash Command Builder
Author: mike-coulbourn

bymike-coulbourn

•

Productivity & Workflow

Builds custom, reusable slash commands for Claude Code to automate repetitive developer workflows and standardize team prompts.

About

The Slash Command Builder skill provides a comprehensive framework for designing and implementing custom commands within the Claude Code CLI environment. It guides users through the entire lifecycle of command creation—from requirements gathering and scope selection (personal vs. project) to implementing advanced features like dynamic arguments, bash execution, and file references. Whether you are looking to automate git workflows, standardize code reviews, or generate boilerplate, this skill ensures your custom commands follow best practices for frontmatter configuration and tool accessibility, making your AI-powered terminal sessions more efficient and consistent.

Key Features

Dynamic argument support ($ARGUMENTS and positional $1, $2)
Step-by-step workflow for designing personal or project-wide automation
Contextual file referencing using the @ syntax for deep code analysis
Integrated bash execution for injecting real-time terminal context into prompts
3 GitHub stars
Standardized frontmatter configuration for tool permissions and help documentation

Use Cases

Building team-wide /review commands that reference specific project style guides and documentation
Designing /generate commands for rapid boilerplate creation with dynamic user inputs
Creating a standardized /commit command that gathers git status and branch info automatically

About

Key Features

Dynamic argument support ($ARGUMENTS and positional $1, $2)
Step-by-step workflow for designing personal or project-wide automation
Contextual file referencing using the @ syntax for deep code analysis
Integrated bash execution for injecting real-time terminal context into prompts
3 GitHub stars
Standardized frontmatter configuration for tool permissions and help documentation

Use Cases

Building team-wide /review commands that reference specific project style guides and documentation
Designing /generate commands for rapid boilerplate creation with dynamic user inputs
Creating a standardized /commit command that gathers git status and branch info automatically