What problem does it solve?
Enables developers to consistently create, organize, and validate Claude Code plugins so components load reliably and plugins remain portable and maintainable across environments.
Core Features & Use Cases
- Manifest rules & validation: Clear requirements for .claude-plugin/plugin.json placement, required fields, semantic versioning, and path resolution to avoid discovery errors.
- Component organization: Conventions and patterns for commands, agents, skills, hooks, MCP servers, and shared libraries to scale from minimal prototypes to enterprise plugins.
- Portable path usage: Guidance on using ${CLAUDE_PLUGIN_ROOT} and ./ relative paths to ensure scripts, hooks, and MCP servers work across installs and OSes.
- Examples & troubleshooting: Real-world plugin examples (minimal, standard, advanced), best practices, and common troubleshooting steps for discovery and path issues.
Quick Start
Scaffold a Claude Code plugin named my-plugin with a .claude-plugin/plugin.json, commands/, agents/, skills/ (each skill with SKILL.md), and use ${CLAUDE_PLUGIN_ROOT} for all internal path references.