Plugin Structure

Topics in the source

• Plugin Structure for Claude Code
• Overview
• Directory Structure
• Plugin Manifest (plugin.json)
• Required Fields
• Recommended Metadata
• Component Path Configuration
• Component Organization

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 Every Claude Code plugin follows this organizational pattern: Critical rules: 1. Manifest location: The plugin.json manifest MUST be in .claude-plugin/ directory 2. Component locations: All component directories (commands, agents, skills, hooks) MUST be at plugin root level, NOT nested inside .claude-plugin/ 3. Optional components: Only create directories for components the plugin actually uses 4. Naming convention: Use kebab-case for all directory and file names The manifest defines plugin metadata and configuration. Located at .claude-plugin/plugin.json: Name requirements: Use kebab-case format (lowercase with hyphens) Must be unique across installed plugins No spaces or spec

This is an excerpt. Refer to the complete source and its current requirements.