What problem does it solve?
Reduce confusion and errors when creating Claude Code plugins by providing clear rules for manifest placement, component locations, naming conventions, path resolution, and auto-discovery so plugins load reliably across environments.
Core Features & Use Cases
- Manifest guidance: Required
.claude-plugin/plugin.json location, recommended fields, semantic versioning, and validation rules for reliable plugin registration.
- Component organization: Conventions for commands, agents, skills, hooks, and MCP servers with examples for flat, categorized, and hierarchical layouts.
- Path resolution & portability: Rules for using ${CLAUDE_PLUGIN_ROOT}, relative
./ paths, and avoiding absolute paths to ensure cross-platform installs.
- Auto-discovery and best practices: How Claude Code discovers components, how to structure SKILL.md files, progressive disclosure for references/examples, and troubleshooting steps for common issues.
- Use case: Plugin authors or teams building reusable plugins for CI/CD, automation, or developer tooling to ensure consistent structure and safe deployment.
Quick Start
Scaffold a new Claude Code plugin with a .claude-plugin/plugin.json and top-level commands/, agents/, skills/, and hooks/ directories using kebab-case names and ${CLAUDE_PLUGIN_ROOT} for internal path references.