command-development

Standardize Claude Code slash command creation with YAML frontmatter and validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps people create clear, reusable Claude Code slash commands that are easy to discover, maintain, and safely execute across projects and plugins.

Core Features & Use Cases

  • Command Structure: Defines how slash command files are organized and written in Markdown with YAML frontmatter.
  • Dynamic Inputs: Explains positional arguments, argument hints, file references, and inline bash execution for context-aware commands.
  • Plugin Patterns: Covers plugin-specific workflows, including portable resource paths, script invocation, skill integration, and validation safeguards.
  • Use Case: A team can use this Skill to design a review, deploy, or documentation command that behaves consistently, exposes the right tools, and handles missing inputs gracefully.

Quick Start

Use the command-development skill to help me design a Claude Code slash command for reviewing code changes with the right frontmatter, arguments, and tool restrictions.

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 Claude Code slash command with YAML frontmatter and dynamic arguments?

To create a Claude Code slash command, you author a Markdown file with YAML frontmatter that defines description metadata, argument-hint mapping, and allowed-tools restriction, then implement positional arguments and inline bash execution for dynamic context-aware workflows.

What is the correct way to structure plugin commands and resource paths in Claude Code?

Plugin commands require portable plugin-root resource paths for referencing scripts and files, along with specific validation safeguards to ensure reliable discovery and safe execution across different plugin environments and team configurations.

How does argument-hint mapping work for Claude Code slash commands?

Argument-hint mapping connects positional dynamic arguments defined in your command structure to user-facing hints, ensuring Claude Code can properly parse inputs, handle missing values gracefully, and pass context to the underlying execution workflow.

Can I restrict which tools a Claude Code slash command is allowed to use?

Yes, you can restrict tool access by specifying the allowed-tools property in the YAML frontmatter, ensuring your custom command only executes permitted bash commands and file operations for safer automation and team distribution.

Why are my custom Claude Code plugin commands not being discovered or executing correctly?

Commands fail discovery or execution when missing required description metadata, using incorrect plugin-root resource paths, or lacking proper validation patterns, which this command-development approach standardizes to ensure reliable behavior.

What's the best way to validate Claude Code commands before deploying them to a team?

The best way to validate commands is by applying safe validation patterns that check frontmatter structure, argument-hint consistency, tool restrictions, and plugin resource paths, ensuring consistent behavior and graceful handling of missing inputs.