command-development

Design and validate reusable Claude Code slash commands with YAML frontmatter.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill command-development-mattmacleod16-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-development
Source: https://github.com/mattmacleod16-svg/freedomforge-max/tree/main/.agents/skills/command-development
Command: npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill command-development-mattmacleod16-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design and integrate reusable slash commands within Claude Code, reducing manual setup time and inconsistency across prompts.

Core Features & Use Cases

  • Structured Command Design: Define slash commands with YAML frontmatter and a consistent prompt format.
  • Reusable Patterns: Share command templates across projects to accelerate automation.
  • Use Case: When building a Claude Code workflow, create a project-wide command library to standardize prompts.

Quick Start

Create a new slash command by adding a Markdown file with YAML frontmatter and a prompt body.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I create reusable slash commands for Claude Code?

Build slash commands by creating a Markdown file with YAML frontmatter containing required name and description fields, then add a prompt body to standardize the command structure for project-wide automation.

What is YAML frontmatter and why is it needed for Claude Code prompts?

YAML frontmatter provides structured metadata for Claude Code prompts by enforcing required name and description fields, enabling consistent command identification and reusable prompt design across developer workflows.

Can I use dynamic arguments in Claude Code slash commands?

Yes, Claude Code slash commands support dynamic arguments within the prompt structure, allowing you to pass variable inputs to customize prompt execution and build flexible developer workflows.

Does this approach support optional scripts or references in command files?

Yes, the slash command structure supports optional scripts, references, and assets alongside the required YAML frontmatter, allowing you to attach supplementary resources to command prompts.

What is the best way to standardize prompt templates across multiple projects?

The best way to standardize prompt templates is building a shared command library using consistent YAML frontmatter and reusable prompt patterns, reducing manual setup time and inconsistency across teams.