Free slash command generator · Runs in your browser

Build a /slash command for Claude Code

Turn your most-repeated prompt into a proper command: frontmatter, $ARGUMENTS, live !`bash` context, and the right file in .claude/commands/ — with a live preview as you type.

/

Give the command a name and a prompt (or load a preset) and the file appears here.

100% client-side · save to .claude/commands/ (project) or ~/.claude/commands/ (personal)

Anatomy

Everything a command file can do

A slash command is a markdown file whose name becomes the command. Four features turn it from a canned prompt into a small program.

📝

Frontmatter

description (shows in /help), argument-hint (autocomplete), allowed-tools (pre-approves the bash the command needs), and optional model.

🧩

Arguments

$ARGUMENTS grabs everything after the command; $1, $2… grab positional args — so /fix-issue 123 high can slot values exactly where they belong.

⚡

Live bash context

Lines like !git diff HEAD`` run before the prompt and inject real output — the command reasons about your actual repo state, not a guess.

📎

File references

@src/utils/helpers.ts inlines a file's contents into the prompt, so commands can review or compare specific files.

Patterns

Commands worth stealing

▹

The context-first command

Put !git status` / !git diff under a ## Context heading, your instructions under ## Task`. The model gets state before instructions — accuracy jumps.

▹

The scoped permissions trick

allowed-tools: Bash(git commit:*) pre-approves exactly the commands your slash command needs and nothing else — no permission prompts, no over-granting.

▹

Namespacing with folders

.claude/commands/frontend/component.md becomes /frontend:component. Group your team's commands by domain instead of one flat pile.

▹

Commit them

Project commands live in the repo, so /commit, /review-pr, and /deploy-check behave identically for every teammate — prompt engineering that ships like code.

FAQ

Slash command questions

Where do slash command files go?+
Project commands: .claude/commands/ in your repo (shared, shown as '(project)' in /help). Personal commands: ~/.claude/commands/ (available in all your projects). Subfolders become namespaces: frontend/component.md → /frontend:component.
Why isn't my !`command` running?+
Two usual causes: the line must start with ! immediately followed by a backticked command, and the command needs to be covered by allowed-tools in the frontmatter (e.g. Bash(git diff:*)).
Can a slash command use a specific model?+
Yes — add model: haiku (or sonnet/opus) to the frontmatter. Cheap models are great for mechanical commands like changelog formatting; keep your default model for judgment calls.
How is this different from a skill?+
Commands are single prompts you invoke explicitly. Skills are folders (SKILL.md + resources) that Claude loads automatically when relevant. If your command keeps growing sections, it probably wants to be a skill — try our SKILL.md validator next.
Is anything uploaded when I use this generator?+
No — it's entirely client-side. Your prompts never leave the browser.
Go further

181 commands, already written

This builder makes one great command. The ClaudeThings kits ship 181 of them — commit flows, review pipelines, deploy checks, content workflows — plus the agents and skills they orchestrate.

🛠️
Most popular

Engineering Kit

Battle-tested Claude skills & workflows for builders.

  • ✓ 58 agents · 61 skills · 159 commands
  • ✓ Security, testing & code-review skills
  • ✓ Every skill formatted to spec
  • ✓ Lifetime updates
Get the Engineering Kit
📣
For founders

Marketing Kit

Turn Claude into your growth team.

  • ✓ 31 agents · 42 skills · 32 commands
  • ✓ Content, SEO & email-sequence skills
  • ✓ Landing-page & funnel templates
  • ✓ Lifetime updates
Get the Marketing Kit

Or grab all 89 agents, 103 skills & 181 commands in the Complete Bundle →