plugin-structure

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDEPLUGINROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

Plugin Structure for Claude Code Overview Claude Code plugins follow a standardized directory structure with automatic component discovery. Understanding this structure enables creating well-organized, maintainable plugins that integrate seamlessly with Claude Code. Key concepts: - Conventional directory layout for automatic discovery - Manifest-driven configuration in .claude-plugin/plugin.json - Component-based organization (commands, agents, skills, hooks) - Portable path references using ${CLAUDEPLUGINROOT} - Explicit vs. auto-discovered component loading Directory Structure Every Claude Code plugin follows this organizational pattern: plugin-name/ ├── .claude-plugin/ │ └── plugin.json Required: Plugin manifest ├── commands/ Slash commands (.md files) ├── agents/ Subagent definitions (.md files) ├── skills/ Agent skills (subdirectories) │ └── skill-name/ │ └── SKILL.md Required for e…