Verified:Website 𝕏@official_taches GitHub

create-slash-commands

Create Claude Code slash commands with YAML frontmatter and XML body templates.

2.0k|410|Updated Nov 13, 2025

Search Tags:#productivity #workflow automation #prompt engineering #claude code #standardization #slash commands #custom commands

Ready to run

npx skills add https://github.com/glittercowboy/taches-cc-resources --skill create-slash-commands

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-slash-commands
Source: https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/create-slash-commands
Command: npx skills add https://github.com/glittercowboy/taches-cc-resources --skill create-slash-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the need to repeatedly type out complex or common prompts, allowing teams to standardize AI-driven workflows and ensure consistent execution of tasks. It transforms multi-step instructions into simple, reusable commands.

Core Features & Use Cases

Reusable Prompts: Define custom /commands that expand into detailed, structured prompts, ensuring consistency across tasks and users.
Dynamic Context & Arguments: Incorporate real-time data (e.g., git status) and user-provided arguments (/fix-issue 123) directly into your commands.
Tool Restrictions: Enhance safety and focus by limiting which tools Claude can use for a specific command (e.g., only git commands for a /commit command).

Quick Start

Create a slash command named /optimize that analyzes the current code for performance issues and suggests three specific optimizations.

Frequently Asked Questions about create-slash-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create reusable prompts with slash commands in Claude Code?▼

Slash commands let you define custom `/command-name` shortcuts that expand into structured prompts. Create a YAML file in `.claude/commands` or `~/.claude/commands` with a frontmatter (description, optional argument-hint) and XML body containing `<objective>`, `<process>`, and `<success_criteria>` sections. Claude Code reads and executes these on demand.

Can I pass arguments to slash commands and use dynamic context?▼

Yes. Slash commands support argument patterns (e.g., `/fix-issue 123`) that inject user input into prompts. You can also load dynamic context like `git status` output or file contents directly into commands, enabling real-time data integration without manual copy-paste.

What's the best way to standardize AI workflows across a team?▼

Slash commands standardize workflows by centralizing reusable prompts in shared `.claude/commands` directories. Teams define consistent task templates once—covering objective, process, success criteria, and tool restrictions—then execute identical commands across projects, reducing variation and ensuring repeatable results.

How do I restrict which tools Claude can use for a specific command?▼

Slash commands support tool restrictions through their XML body configuration, allowing you to specify which tools (e.g., only `git` commands) Claude can access for that command. This enhances safety and focus by limiting Claude's capabilities to the task at hand.

Do slash commands require special file structure or naming conventions?▼

Slash commands follow a standard structure: YAML frontmatter with description and optional argument-hint, plus XML body with `<objective>`, `<process>` or `<steps>`, `<success_criteria>`, and optional `<context>`, `<verification>`, and `<output>` sections. Files live in `.claude/commands` or `~/.claude/commands` directories.

What limits should I know when using slash commands for workflow automation?▼

Slash commands are basic-depth tools focused on prompt standardization and reuse. Complex multi-tool orchestration or advanced conditional logic beyond argument patterns may require supplementary automation. Commands inherit Claude Code's capabilities and constraints.