Plugin Structure

Documents Claude Code plugin architecture, including directory structure and manifest configuration.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Agentic-Assets/apple-mail-mcp --skill plugin-structure-agentic-assets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/Agentic-Assets/apple-mail-mcp/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/Agentic-Assets/apple-mail-mcp --skill plugin-structure-agentic-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and examples (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to Claude Code plugin architecture, directory structure, and best practices, enabling developers to create well-organized, maintainable plugins that integrate seamlessly with Claude Code.

Core Features & Use Cases

  • Plugin Directory Structure: Detailed explanation of the standardized directory layout for Claude Code plugins.
  • Manifest Configuration: Guidance on the plugin.json manifest, including required and recommended fields.
  • Component Organization: Information on organizing commands, agents, skills, hooks, and scripts within a plugin.
  • Auto-Discovery Mechanism: Explanation of how Claude Code automatically discovers and loads plugin components.
  • Best Practices: Best practices for plugin organization, naming conventions, portability, and maintenance.
  • Common Patterns: Examples of minimal, standard, and advanced plugin structures.
  • Troubleshooting: Guidance on common issues like component loading, path resolution, and auto-discovery problems.

Quick Start

Run the 'create-plugin' command to get started with building a Claude Code plugin.

Frequently Asked Questions about Plugin Structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Claude Code plugin directory?

A Claude Code plugin directory requires a standardized layout organizing commands, agents, skills, hooks, and scripts. This guide details the exact directory structure and manifest configuration needed for seamless integration and maintainability.

What is the best way to configure a Claude Code plugin manifest?

Configuring a Claude Code plugin manifest involves defining required and recommended fields within the `plugin.json` file. Proper manifest configuration ensures the plugin components are correctly organized and recognized by the system.

How does auto-discovery work for Claude Code plugin components?

Auto-discovery for Claude Code plugin components works by automatically detecting and loading organized commands, agents, and hooks based on the standardized directory structure. This mechanism simplifies plugin integration without manual registration.

Do I need prior knowledge of Claude Code to develop plugins?

Yes, developing Claude Code plugins requires existing knowledge of Claude Code and plugin development concepts. This guide focuses on architecture, directory structure, and best practices rather than introductory concepts.

What are the common patterns for Claude Code plugin architecture?

Common patterns for Claude Code plugin architecture include minimal, standard, and advanced directory structures. These patterns provide templates for organizing components based on specific project complexity and requirements.

Why is my Claude Code plugin not loading components properly?

Claude Code plugin components may fail to load due to auto-discovery problems or incorrect path resolution. This guide provides troubleshooting steps for common component loading issues and manifest configuration errors.