command-development

Design, document, and validate Claude Code slash commands for plugins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables the design, documentation, and validation of Claude Code slash commands for plugins, ensuring consistent patterns and reusable templates across teams.

Core Features & Use Cases

  • Frontmatter-driven configuration: Apply YAML frontmatter fields (description, allowed-tools, model, argument-hint, etc.) to command files for discovery and automation.
  • Command anatomy and patterns: Learn command structure, namespacing, and plugin command patterns (configuration-based, template-based, multi-script).
  • Dynamic arguments and references: Implement $ARGUMENTS, $1, $2, and file references using @ syntax to compose context-aware prompts.
  • Bash execution & tooling: Use BANG` syntax for deterministic context gathering and safe shell integration.
  • Plugin ecosystem integration: Coordinate with agents, skills, hooks, and plugin resources to enable multi-file workflows.
  • Validation, testing & maintenance: Guidance on input validation, error handling, testing strategies, and documentation best practices.

Quick Start

Use the command-development skill to outline and implement a new plugin slash command by creating a Markdown file with minimal frontmatter and expanding it with structured content following the patterns described in this skill.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I configure YAML frontmatter for Claude Code slash commands?

Configure slash commands by applying YAML frontmatter fields such as description, allowed-tools, model, and argument-hint to Markdown command files for automated discovery and execution.

How do I pass dynamic arguments to plugin commands using $ARGUMENTS?

Pass dynamic arguments using $ARGUMENTS, $1, and $2 variables within your command files, and use @ syntax for file references to compose context-aware prompts that accept user input dynamically.

What is the best way to structure a multi-script plugin command?

The best way to structure multi-script plugin commands is using established command anatomy patterns, organizing configuration-based and template-based components into a resource directory with scripts, references, and assets.

How do I execute Bash commands safely within a Claude Code plugin?

Execute Bash commands safely by using BANG syntax for deterministic context gathering, ensuring secure shell integration and validated input handling within your plugin's command execution environment.

Can I use this command-development approach without existing plugin dependencies?

Yes, you can use this approach without external dependencies because it requires only a Markdown file with minimal frontmatter, allowing you to expand structured content and validate commands independently.

Why does my Claude Code slash command fail validation during plugin integration?

Slash command validation fails when mandatory SKILL.md frontmatter is missing, or when input validation, error handling, and argument-hint configurations do not follow the required plugin integration patterns.