plugin-structure

To structure a Claude Code plugin for auto-discovery, organize components like commands, agents, skills, and hooks into a standard directory layout with a clear SKILL.md entry point for each skill. This ensures automated component detection and reduces misconfiguration.

The recommended directory layout for Claude Code plugins separates commands, agents, skills, and hooks into distinct directories, guided by a manifest for component organization. This standard scaffolding simplifies plugin creation and ensures cross-environment compatibility.

Use portable paths like ${CLAUDE_PLUGIN_ROOT} in your Claude Code plugin manifest to ensure cross-environment compatibility. This variable reference prevents hardcoded paths from breaking component discovery when plugins are deployed across different systems.

The plugin manifest should be placed at the root of your Claude Code plugin directory structure to govern component discovery and organization. Correct manifest placement is critical for automated auto-discovery of commands, agents, and skills.

Scaffolding a Claude Code plugin using this structure pattern requires no external dependencies. You can copy a clean plugin skeleton into your project and begin adding commands, agents, and skills following the documented conventions.

Claude Code plugin component discovery fails across environments when directory structures are inconsistent or paths are hardcoded. Standardizing the layout and using portable path references like ${CLAUDE_PLUGIN_ROOT} resolves these cross-environment compatibility issues.