Plugin Structure

Name: Plugin Structure
Availability: InStock
Author: arlenagreer

Standardize Claude Code plugin directory structure and manifest configuration.

Updated Aug 23, 2026

Search Tags:#architecture #plugin development #component organization #auto-discovery #manifest configuration

One-click install

npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill plugin-structure-arlenagreer

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/arlenagreer/claude_configuration_docs/tree/main/plugins/marketplaces/claude-code-plugins/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill plugin-structure-arlenagreer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates confusion around plugin development by providing comprehensive guidance on directory structure, component organization, and best practices.

Core Features & Use Cases

Comprehensive Architecture: Detailed guidance on plugin directory layout, manifest configuration, and auto-discovery mechanisms.
Component Organization: Best practices for structuring commands, agents, skills, hooks, and MCP servers.
Use Case: Imagine you want to create a new plugin for code reviews. Use this Skill to understand how to organize your commands, agents, and skills for optimal performance and maintainability.

Quick Start

Use the Plugin Structure skill to create a new plugin directory with the correct structure and manifest configuration.

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?▼

Plugin structure follows a standardized layout with a manifest file at the root, organized subdirectories for commands, agents, skills, and hooks, and kebab-case naming conventions. The manifest defines metadata and auto-discovery rules that determine how Claude Code loads your plugin components.

What goes in a plugin manifest configuration?▼

The manifest specifies plugin metadata, component paths, naming rules, and auto-discovery settings. It can use default paths or custom configurations and must be placed at the plugin root to enable Claude Code to locate and load commands, agents, skills, hooks, and MCP servers correctly.

How do I organize commands, agents, and skills within a plugin?▼

Organize each component type into dedicated directories with kebab-case file naming. This component organization enables predictable auto-discovery, maintains portable path references across environments, and ensures Claude Code can resolve and load extensions without manual registration.

Can I use MCP servers within a plugin?▼

Yes. MCP server integration is part of the standardized plugin architecture. Configure MCP servers in your manifest alongside other components, following the same directory structure and naming conventions as commands, agents, and skills.

What happens if my plugin directory structure doesn't match the standard?▼

Non-standard structures prevent auto-discovery and may cause loading failures. Following the standardized layout—manifest placement, kebab-case naming, and organized component directories—ensures Claude Code correctly recognizes and loads all plugin extensions.