Plugin Structure

Explain Claude Code plugin structure including commands, agents, skills, hooks, and manifest configuration.

6|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/pur3v4d3r/pur3-pkb-codebase --skill plugin-structure-pur3v4d3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/pur3v4d3r/pur3-pkb-codebase/tree/main/.claude/skills/plugin-structure
Command: npx skills add https://github.com/pur3v4d3r/pur3-pkb-codebase --skill plugin-structure-pur3v4d3r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured blueprint for understanding and implementing Claude Code plugin architectures, including discovery, manifest configuration, and component organization.

Core Features & Use Cases

  • Establishes a canonical directory layout for Claude Code plugins (commands, agents, skills, hooks)
  • Documents auto-discovery rules and manifest-driven loading to simplify integration
  • Provides references and examples to accelerate learning and standardize practice
  • Enables consistent maintenance and onboarding for plugin development teams

Quick Start

Describe the standard plugin structure and trigger auto-discovery.

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?

Claude Code plugins use a canonical directory layout that organizes commands, agents, skills, and hooks. This structure relies on a manifest configuration file to drive loading and simplify component integration.

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

Auto-discovery in Claude Code operates through manifest-driven loading rules that automatically scan and register plugin components. This eliminates manual configuration by standardizing how directories are parsed during setup.

Do I need frontmatter configuration for Claude Code plugin skills?

Yes, frontmatter is a strict requirement for Claude Code plugin skills. Defining frontmatter correctly ensures the auto-discovery mechanism can properly identify, parse, and load the skill components.

How do I organize cross-resource references when building a Claude Code plugin?

Cross-resource organization in Claude Code plugins is managed through the standard directory layout and manifest configuration. This ensures commands, agents, and hooks reference each other predictably without breaking discovery.

Can I integrate MCP servers within my Claude Code plugin structure?

Yes, MCP integration is supported within the Claude Code plugin structure. You define MCP connections in the manifest file, allowing your plugin components to communicate with external servers seamlessly.

What are the limitations of manifest-driven loading for Claude Code plugins?

Manifest-driven loading requires strict adherence to auto-discovery rules and frontmatter requirements. If components deviate from the canonical directory layout, the plugin structure may fail to load or organize properly.