plugin-structure

Explain Claude Code plugin directory layout, component types, and naming conventions.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Prirogativus/devlab --skill plugin-structure-prirogativus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/Prirogativus/devlab/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/Prirogativus/devlab --skill plugin-structure-prirogativus

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive knowledge about Claude Code plugin architecture, directory layout, and best practices, enabling users to create well-organized, maintainable plugins that integrate seamlessly with Claude Code.

Core Features & Use Cases

  • Plugin Directory Structure: Offers an in-depth explanation of the conventional directory layout for automatic discovery in Claude Code.
  • Plugin Manifest Configuration: Details the plugin.json manifest configuration, including required and recommended metadata fields.
  • Component Organization: Explains the organization of components such as commands, agents, skills, hooks, and MCP servers.
  • File Naming Conventions: Provides guidelines for naming conventions for directory and file names within Claude Code plugins.
  • Auto-Discovery Mechanism: Describes how Claude Code automatically discovers and loads components.
  • Best Practices: Offers best practices for organization, naming, portability, and maintenance of plugins.
  • Use Case: A developer looking to create a new Claude Code plugin can use this Skill to understand the structure and best practices for organizing their plugin.

Quick Start

Run the skill by typing "/plugin-structure" in Claude Code.

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 for auto-discovery?

Claude Code plugins require a conventional directory layout that organizes components like commands, agents, skills, hooks, and MCP servers into specific folders. This structure ensures the framework automatically discovers and loads them.

What is the plugin.json manifest configuration used for in Claude Code?

The plugin.json manifest configuration defines required and recommended metadata fields for your plugin. It provides the essential information Claude Code needs to properly recognize and integrate your plugin components.

What file naming conventions should I use for Claude Code plugin components?

File naming conventions for Claude Code plugin components dictate how directories and files are named to ensure portability and maintenance. Adhering to these guidelines prevents auto-discovery issues and keeps your plugin organized.

Does creating a Claude Code plugin require basic knowledge of plugin development?

Yes, understanding Claude Code plugin architecture requires basic knowledge of Claude Code and plugin development. This foundational knowledge is necessary to effectively apply the directory layout and auto-discovery mechanisms.

What are the best practices for organizing commands, agents, and MCP servers in a Claude Code plugin?

Best practices for organizing components in a Claude Code plugin involve following the conventional directory layout and file naming conventions. This approach ensures your commands, agents, skills, hooks, and MCP servers remain portable and maintainable.

When should I reorganize my Claude Code plugin directory layout?

You should reorganize your Claude Code plugin directory layout when your current structure fails to support auto-discovery or violates best practices for naming, portability, and maintenance. Proper component organization ensures seamless integration.