plugin-structure

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

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill plugin-structure-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill plugin-structure-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of building, organizing, and configuring Claude Code plugins, ensuring that developers follow standardized patterns for auto-discovery and component integration.

Core Features & Use Cases

  • Standardized Architecture: Provides a clear blueprint for directory layouts, manifest configuration, and component organization.
  • Component Lifecycle Management: Explains how to effectively manage commands, agents, skills, and hooks to ensure seamless plugin activation.
  • Use Case: When building a new enterprise-grade plugin, use this skill to correctly structure your manifest, implement portable path references using the plugin root variable, and organize your MCP servers for optimal performance.

Quick Start

Use the plugin-structure skill to scaffold a new plugin directory with the required manifest and component folders.

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 and integration?

To structure a Claude Code plugin for auto-discovery, you need a standardized directory layout and a properly configured manifest. This ensures commands, agents, skills, and hooks are organized for seamless component lifecycle management.

What is the best way to organize commands, agents, and hooks in a plugin manifest?

The best way to organize commands, agents, and hooks is by following a standardized architecture blueprint for your directory layout. This component organization ensures seamless plugin activation and correct auto-discovery during the component lifecycle.

How do I implement portable path references when developing a plugin?

To implement portable path references during plugin development, you use the plugin root variable within your manifest configuration. This approach adheres to best practices and ensures your directory structure remains stable across different environments.

Do I need a specific directory layout to manage MCP servers in an enterprise-grade plugin?

Yes, an enterprise-grade plugin requires a specific directory layout to organize MCP servers for optimal performance. Using a standardized architecture blueprint ensures your manifest configuration supports seamless integration and component lifecycle management.

When do I need to configure a manifest for Claude Code plugin development?

You need to configure a manifest whenever you are scaffolding a new plugin directory for Claude Code. This configuration is required to define the component lifecycle and ensure adherence to plugin development best practices.

Why does my Claude Code plugin fail to auto-discover components?

Claude Code plugin auto-discovery fails when the directory layout and manifest configuration do not adhere to standardized architecture patterns. Correctly organizing commands, agents, skills, and hooks in the required component folders resolves this integration issue.