plugin-structure

Explain Claude Code plugin architecture, directory layout, and manifest configuration.

12|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jorgeasaurus/agent-skills --skill plugin-structure-jorgeasaurus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/jorgeasaurus/agent-skills/tree/main/plugin-structure
Command: npx skills add https://github.com/jorgeasaurus/agent-skills --skill plugin-structure-jorgeasaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit offers detailed guidance on the structure, configuration, and maintenance of Claude Code plugins, making it easier to develop and manage advanced plugin functionalities.

Core Features & Use Cases

  • Plugin Architecture: Understand the directory structure, component organization, and best practices for Claude Code plugins.
  • Manifest Configuration: Learn how to define plugin metadata and configuration using the plugin.json manifest.
  • Component Organization: Explore patterns for organizing commands, agents, skills, hooks, and MCP servers.
  • Auto-Discovery: Discover how Claude Code automatically loads components based on directory structure and configuration.
  • Best Practices: Follow guidelines for organization, naming, portability, and maintenance of plugins.
  • Common Patterns: Implement minimal, standard, and skill-focused plugins.
  • Advanced Use Case: Create a complex, enterprise-grade plugin with MCP integration and advanced organization.

Quick Start

To get started with the plugin structure skill, refer to the SKILL.md file within the plugin directory for a comprehensive overview of the plugin's structure and functionality.

Frequently Asked Questions about plugin-structure

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

FAQPage Schema
What is the directory layout for a Claude Code plugin?

Claude Code plugin directory layout organizes components like commands, agents, skills, hooks, and MCP servers into a structured hierarchy. This architecture enables auto-discovery mechanisms where the system automatically loads components based on their directory placement.

How do I configure a Claude Code plugin manifest?

Configure Claude Code plugins using the plugin.json manifest to define metadata and configuration. This manifest specifies plugin details, component organization, and portable path references that ensure cross-environment compatibility and proper auto-discovery.

How does auto-discovery work when loading Claude Code plugin components?

Claude Code auto-discovery loads plugin components automatically based on directory structure and configuration settings. By following specific file naming conventions and component organization patterns, the system detects and registers commands, agents, skills, hooks, and MCP servers without manual intervention.

What are the best practices for Claude Code plugin maintenance and naming conventions?

Claude Code plugin best practices cover organization, naming, portability, and maintenance guidelines. Following portable path references and consistent file naming conventions ensures plugins remain maintainable, discoverable, and compatible across different environments and enterprise configurations.

Do I need prior knowledge of the Claude Code plugin system to use this guide?

Yes, this guide requires understanding of the Claude Code plugin system. It provides in-depth knowledge about advanced architecture, manifest configuration, and component organization, making it suitable for developers building standard or enterprise-grade plugins with MCP integration.

What common patterns exist for structuring minimal versus enterprise-grade Claude Code plugins?

Claude Code plugin patterns range from minimal and standard layouts to skill-focused and enterprise-grade architectures. Enterprise-grade implementations incorporate MCP integration and advanced organization, while minimal patterns provide simplified structures for basic plugin functionality.