Plugin Structure

Organize Claude Code plugin directories, manifests, and components.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill plugin-structure-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/ajsai47/holyclaude/tree/main/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/ajsai47/holyclaude --skill plugin-structure-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the confusion around Claude Code plugin architecture by providing clear guidance on directory layout, manifest configuration, and component organization, saving developers hours of trial and error.

Core Features & Use Cases

  • Plugin Architecture Guidance: Comprehensive coverage of directory structure, plugin.json manifest fields, and component organization patterns for commands, agents, skills, and hooks.
  • Best Practices & Patterns: Detailed references for manifest configuration, component lifecycle, auto-discovery mechanisms, and scalable organization patterns.
  • Use Case: Imagine you need to create a plugin with multiple commands, agents, and skills. Use this Skill to understand the proper directory layout, configure the manifest correctly, and organize components for automatic discovery.

Quick Start

Use the Plugin Structure skill to create a new plugin directory with the proper .claude-plugin folder, manifest configuration, and component organization.

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 for commands, agents, and hooks?

A Claude Code plugin directory requires a .claude-plugin folder with a plugin.json manifest, alongside organized directories for individual commands, agents, skills, and hooks to enable automatic component discovery.

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

The plugin.json manifest configures core plugin architecture in Claude Code, declaring component organization, enabling auto-discovery mechanisms, and defining lifecycle patterns for commands, agents, skills, and hooks.

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

Claude Code plugin auto-discovery works by scanning the standardized directory structure and reading the plugin.json manifest to automatically load properly organized commands, agents, skills, and hooks without manual registration.

What's the best way to organize multiple skills and commands in a Claude Code plugin?

The best way to organize multiple components in a Claude Code plugin is to follow established directory structure conventions, using portable path references in the plugin.json manifest and grouping commands, agents, and skills into scalable folder hierarchies.

Do I need to manually configure paths for each hook and command in my plugin manifest?

No, you do not need to manually configure paths for each hook and command if you follow the recommended directory structure, because Claude Code uses auto-discovery mechanisms to locate components configured with portable path references in the manifest.