plugin-structure

Claude Code plugin structure requires a standardized directory layout for commands, agents, skills, and hooks, along with a `.claude-plugin/plugin.json` manifest to map component paths and enable predictable auto-discovery.

Manifest configuration for Claude Code plugins requires a `.claude-plugin/plugin.json` file to define metadata and path mappings, enabling the loader to automatically discover and register commands, agents, skills, and hooks.

Auto-discovery for plugin components works by scanning default and custom directory locations specified in the manifest, automatically loading commands, agents, skills, and hooks that contain mandated YAML frontmatter with name and description.

Yes, YAML frontmatter is required for Claude Code plugin skills to load correctly, as the auto-discovery mechanism mandates that each skill file includes frontmatter with a name and description to be recognized and registered.

The best way to reference plugin paths across different platforms is to use the `${CLAUDE_PLUGIN_ROOT}` variable, which ensures portable path references for components and resources regardless of the underlying operating system.

Yes, you can use custom directory locations for plugin components instead of defaults by explicitly mapping the custom paths in your `.claude-plugin/plugin.json` manifest, which the auto-discovery mechanics support for smooth loading.