What problem does it solve?
Help plugin authors avoid fragmentation, misconfiguration, and brittle installations by providing a clear, opinionated structure and operational rules for Claude Code plugins so components load reliably and paths resolve portably.
Core Features & Use Cases
- Manifest and Validation: Specifies required
.claude-plugin/plugin.json placement, required fields, versioning, and path resolution rules to prevent load-time errors.
- Component Organization: Defines canonical locations and formats for commands, agents, skills (SKILL.md), hooks, and MCP servers and how auto-discovery works.
- Portability & Paths: Explains using ${CLAUDE_PLUGIN_ROOT} and relative paths, plus naming conventions (kebab-case) to ensure cross-platform installs.
- Operational Patterns & Troubleshooting: Offers examples for minimal, standard, and advanced plugins, hook registration patterns, MCP server integration, and common validation fixes.
Quick Start
Scaffold a new Claude Code plugin by creating a .claude-plugin/plugin.json, commands/, agents/, skills/<skill>/SKILL.md, and hooks/ using kebab-case names and ${CLAUDE_PLUGIN_ROOT} for all internal paths.