What problem does it solve?
Guiding developers to design and organize Claude Code plugins by providing a canonical directory layout, manifest rules, and auto-discovery behavior so teams can scale plugin development with consistency.
Core Features & Use Cases
- Clear, conventional directory structure: plugin root with .claude-plugin/plugin.json, and separate commands/, agents/, skills/, hooks/ and optional scripts/, references/, assets/ directories.
- Manifest-driven configuration: central plugin.json in .claude-plugin and optional inline or external wiring for hooks and MCP servers.
- Component organization and auto-discovery: predictable loading of commands, agents, skills (via SKILL.md), and MCP integrations.
- Portable path references: use ${CLAUDE_PLUGIN_ROOT} to keep paths environment-agnostic and cross-platform.
- Real-world templates: pattern examples for minimal, full-featured, and plugin-within-a-plugin structures to speed adoption.
Quick Start
Create a new plugin folder with a .claude-plugin/plugin.json and at least one command under commands/ to begin discovery.