Command Development

To create a Claude Code slash command, you design a prompt with a frontmatter-driven contract where name and description fields are mandatory, optionally adding resource directories, validation hooks, and marketplace-ready metadata for safe plugin integration.

The best way to structure a plugin command workflow is using centralized frontmatter-driven command templates that enforce consistent patterns, integrate agents and hooks safely, and include reference sections for deeper guidance and troubleshooting.

Yes, you can use interactive commands with agents and hooks in Claude Code plugins by applying frontmatter-driven configuration patterns that orchestrate scripts, validate safety, and ensure consistent integration across plugin-based workflows.

Yes, you need mandatory frontmatter fields like name and description to distribute commands on a marketplace. The frontmatter-driven contract includes versioning and marketplace-ready metadata considerations to ensure safe and scalable distribution.

Your Claude Code plugin command likely fails validation because it lacks the mandatory frontmatter-driven contract fields, proper resource directory references, or safety checks required for orchestrating scripts, agents, and hooks in automation workflows.

You need frontmatter-driven configuration for slash command development when scaling plugin-based workflows, interacting with agents and hooks, or preparing commands with versioning and metadata for marketplace distribution and safe integration.