Plugin Structure

Explain the standardized directory structure and plugin.json manifest configuration for Claude Code plugins.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/CuCryptos/sixroundsdeep --skill plugin-structure-cucryptos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/CuCryptos/sixroundsdeep/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/CuCryptos/sixroundsdeep --skill plugin-structure-cucryptos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to organizing and structuring Claude Code plugins, ensuring discoverability, maintainability, and seamless integration.

Core Features & Use Cases

  • Directory Layout: Understand the conventional structure for commands, agents, skills, and hooks.
  • Manifest Configuration: Learn to configure plugin.json for metadata and custom paths.
  • Component Organization: Best practices for naming and structuring different plugin parts.
  • Use Case: When starting a new plugin project, use this Skill to set up the correct directory structure and understand how to configure the plugin.json manifest for optimal discoverability and functionality.

Quick Start

Use the plugin structure skill to understand the standard directory layout for a Claude Code plugin.

Frequently Asked Questions about Plugin Structure

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

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

The standard Claude Code plugin directory structure organizes commands, agents, skills, hooks, and MCP servers into conventional folders. This layout ensures component discoverability, maintainability, and seamless integration through auto-discovery mechanisms.

How do I configure the plugin.json manifest for optimal component organization?

Configuring the plugin.json manifest involves defining metadata and custom paths for your Claude Code plugin. This file directs the auto-discovery mechanisms to correctly identify and load commands, agents, skills, and hooks.

What are the naming conventions for Claude Code plugin components?

Naming conventions for Claude Code plugin components emphasize standardized structures for commands, agents, skills, and hooks. Adhering to these best practices ensures portability and maintainability across different plugin projects.

When do I need to use custom paths in my plugin manifest?

Custom paths in a plugin manifest are needed when your directory structure deviates from the conventional layout. Configuring plugin.json allows you to specify these custom locations while maintaining seamless integration and auto-discovery.

Does Claude Code plugin architecture support MCP servers and hooks?

Claude Code plugin architecture fully supports MCP servers and hooks alongside commands, agents, and skills. The standardized directory structure ensures these components are automatically discovered and integrated into the system.