What problem does it solve? Building a Claude Code plugin requires knowing the exact directory layout, manifest fields, and auto-discovery rules, and getting any of these wrong means components silently fail to load. ## Core Features & Use Cases - Directory Layout Guidance: Explains the required .claude-plugin/plugin.json location and root-level component directories for commands, agents, skills, and hooks. - Manifest Reference: Documents every plugin.json field including name, version, author, custom component paths, and path resolution rules. - Portable Path Patterns: Shows how to use ${CLAUDE_PLUGIN_ROOT} so hooks, MCP servers, and scripts work regardless of install location. - Use Case: You want to scaffold a new plugin with a slash command, a subagent, and a PreToolUse hook; this skill walks you through the manifest, file naming conventions, and auto-discovery behavior so everything registers correctly on the first try. ## Quick Start Ask Claude to scaffold a new Claude Code plugin with a command, an agent, and a hook, following the standard plugin directory structure.
