Command Development

Create and integrate Claude Code slash commands with frontmatter configuration.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/lusya123/cloudcode --skill command-development-lusya123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Command Development
Source: https://github.com/lusya123/cloudcode/tree/main/claude-code-main/plugins/plugin-dev/skills/command-development
Command: npx skills add https://github.com/lusya123/cloudcode --skill command-development-lusya123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Command Development standardizes how teams create, document, and share Claude Code slash commands. It guides frontmatter configuration, dynamic argument handling, file references, and integration with plugin components to ensure consistent, scalable prompts.

Core Features & Use Cases

  • Frontmatter-driven command configuration and validation
  • Support for dynamic arguments (ARGUMENTS, $1, $2), file references (@ syntax), and Bash execution for inline context
  • Plugin integration with agents, skills, and hooks for complex workflows
  • Clear command organization with namespacing and plugin-scoped commands
  • Progressive references and examples to accelerate adoption

Quick Start

Create a new Markdown command file under .claude/commands with a YAML frontmatter block and a plain prompt body following 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 create a slash command for Claude Code plugins?

Create a slash command by adding a Markdown file under .claude/commands with a YAML frontmatter block defining the name and description, followed by a plain prompt body.

How do I use dynamic arguments and file references in command development?

Command development supports dynamic arguments using ARGUMENTS, $1, $2 syntax, file references via @ syntax, and Bash execution to inject inline context into your prompts.

What is frontmatter configuration and why is it needed for slash commands?

Frontmatter configuration uses YAML to standardize command metadata like name and description. It is required to validate and integrate commands properly within plugin workflows.

Can I integrate agents, skills, and hooks with my custom commands?

Yes, slash commands support plugin integration with agents, skills, and hooks, enabling you to build complex and scalable workflows across different plugin components.

Do I need any external dependencies to build and validate commands?

No external dependencies are required. You only need a SKILL.md frontmatter with name and description, alongside optional scripts, references, and assets directories for organization.