command-development

Create Claude Code slash commands with YAML frontmatter and Bash execution patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hgonzalezstahl-blip/claude-arsenal --skill command-development-hgonzalezstahl-blip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-development
Source: https://github.com/hgonzalezstahl-blip/claude-arsenal/tree/main/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/command-development
Command: npx skills add https://github.com/hgonzalezstahl-blip/claude-arsenal --skill command-development-hgonzalezstahl-blip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized blueprint for creating Claude Code slash commands, ensuring consistent frontmatter, structure, and patterns across projects and plugins.

Core Features & Use Cases

  • YAML frontmatter-driven command configuration (description, allowed-tools, model, argument-hint, etc.)
  • Dynamic arguments, file references, and Bash execution patterns for flexible prompts
  • Plugin integration guidance (agents, skills, hooks) and namespace-enabled command organization

Quick Start

Create a new command file under .claude/commands/, start with minimal frontmatter, and gradually expand with required fields as you scale.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I create Claude Code slash commands with consistent YAML frontmatter?

Claude Code slash commands are created by defining standard YAML frontmatter fields like description, allowed-tools, and model in a file under .claude/commands/ to ensure consistent configuration across projects and plugins.

Can I use dynamic arguments and file references in Claude Code commands?

Dynamic arguments and file references are supported in Claude Code commands through frontmatter-driven patterns, allowing flexible prompt construction that can also execute Bash commands and integrate with agents, skills, and hooks.

What is the best way to standardize slash command patterns across plugins?

Standardizing slash command patterns across plugins requires a repeatable frontmatter-driven blueprint that applies validation rules, resource references, and namespace-enabled organization to both plugin and project commands.

Does this command development approach work for both project and plugin commands?

Yes, this command development approach applies to both project and plugin commands by covering YAML frontmatter configuration, dynamic arguments, and integration guidance for agents, skills, and hooks within a structured Skill unit.

How do I organize Claude Code commands using namespaces?

Namespace-enabled command organization is handled through the frontmatter-driven blueprint, allowing you to structure and categorize both plugin and project commands logically for discovery and reuse.

What validation patterns are available for Claude Code command configuration?

Validation patterns for Claude Code command configuration are implemented within the structured Skill unit, ensuring proper frontmatter fields, resource references, and cross-file patterns are correctly applied before deployment.