Plugin Structure

Outline Claude Code plugin architecture, directory structure, and manifest configuration.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jmolz/m0lz.02 --skill plugin-structure-jmolz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/jmolz/m0lz.02/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/jmolz/m0lz.02 --skill plugin-structure-jmolz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users understand and implement Claude Code plugins efficiently, providing guidance on directory structure, manifest configuration, and component organization.

Core Features & Use Cases

  • Directory Structure: Detailed overview of the standardized layout for Claude Code plugins.
  • Manifest Configuration: Instructions on defining plugin metadata and component paths.
  • Component Organization: Guidelines for organizing commands, agents, skills, hooks, and MCP servers.
  • Auto-Discovery: Explanation of how Claude Code automatically discovers and loads components.
  • Best Practices: Recommendations for plugin design, naming conventions, portability, and maintenance.
  • Use Case: A developer looking to create a new Claude Code plugin can use this skill to understand the necessary structure and configuration.

Quick Start

Initialize a new Claude Code plugin by using the plugin-structure skill.

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 uses a standardized layout with scripts, references, and assets. This structure organizes commands, agents, skills, hooks, and MCP servers, ensuring components are discoverable and maintainable.

What is manifest configuration in Claude Code plugins?

Manifest configuration in Claude Code plugins defines plugin metadata and component paths. It drives the loading process, allowing developers to explicitly specify components or rely on automated discovery.

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

Auto-discovery in Claude Code plugins automatically finds and loads components based on the standardized directory structure. This lets developers add commands, agents, and hooks without explicitly listing each one in the manifest.

What's the best way to organize Claude Code plugin components?

The best way to organize Claude Code plugin components is using a component-based structure with portable path references. Following naming conventions and separating commands, agents, skills, and hooks ensures maintainability.

Do I need a manifest file for every Claude Code plugin?

A manifest file is needed for Claude Code plugins to define metadata and configure component loading paths. While auto-discovery handles some components, the manifest provides explicit configuration and portability.

When should I use explicit component loading versus auto-discovery in Claude Code?

Use explicit component loading when you need precise control over which Claude Code components activate, and use auto-discovery for rapid development. Explicit configuration offers predictability while auto-discovery reduces maintenance overhead.