Plugin Structure

To structure a Claude Code plugin for reliable auto-discovery, follow a canonical directory layout with a properly configured plugin.json manifest, organizing components like commands, agents, skills, and hooks in their designated folders.

The best way to scaffold a new Claude Code plugin is to create a minimal directory structure containing a manifest file and a basic commands directory, ensuring standardized naming and portable path references from the start.

The ${CLAUDE_PLUGIN_ROOT} variable provides a portable path reference within your plugin structure, ensuring that file references remain stable and correctly resolved regardless of where the plugin is installed.

When building a Claude Code plugin, you need to organize components such as commands, agents, skills, and hooks, placing them in standardized directories to ensure the system can automatically discover and load them.

If your Claude Code plugin is not loading correctly, it is likely due to incorrect manifest placement, improper file naming conventions, or non-standard directory structure that prevents the auto-discovery mechanism from finding your components.

Yes, the Plugin Structure standard provides best-practice documentation patterns and architectural guidance, allowing development teams to maintain consistent plugin organization and reduce integration friction across projects.