Plugin Structure

Standardize Claude Code plugin structure with manifests and component directories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jasonsie/prompt-dev --skill plugin-structure-jasonsie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/jasonsie/prompt-dev/tree/main/skills/plugin-structure
Command: npx skills add https://github.com/jasonsie/prompt-dev --skill plugin-structure-jasonsie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized blueprint for Claude Code plugin architecture, ensuring consistent manifests, component layout, and reliable auto-discovery across projects.

Core Features & Use Cases

  • Standard directory layout for plugins (commands/, agents/, skills/, hooks/) and a required .claude-plugin/plugin.json manifest.
  • Auto-discovery and load-time integration with Claude Code, including portable path references like ${CLAUDE_PLUGIN_ROOT}.
  • Clear guidelines for naming, manifests, and cross-component collaboration to enable scalable plugin development.

Quick Start

Create a new plugin by placing a .claude-plugin/plugin.json at the root and organizing components under commands/, agents/, skills/, and hooks/ so Claude Code can auto-discover and load them.

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?

To structure a Claude Code plugin for auto-discovery, place a .claude-plugin/plugin.json manifest at the root and organize components under commands/, agents/, skills/, and hooks/ directories so Claude Code can automatically load them.

What is the required manifest location for Claude Code plugins?

The required manifest location for Claude Code plugins is the .claude-plugin/plugin.json file at the plugin root, which enables manifest validation and standardizes component organization for reliable load-time integration.

How do I handle portable path references in a Claude Code plugin?

Portable path references in a Claude Code plugin use the ${CLAUDE_PLUGIN_ROOT} variable, ensuring consistent path handling across different environments during auto-discovery and load-time integration.

Does Claude Code plugin architecture support hooks and agents together?

Yes, Claude Code plugin architecture supports hooks and agents together by standardizing a directory layout that includes dedicated commands/, agents/, skills/, and hooks/ folders for scalable cross-component collaboration.

Why does my Claude Code plugin fail to load components automatically?

Claude Code plugins fail to auto-discover components when the .claude-plugin/plugin.json manifest is missing from the root or when files are not organized into the required commands/, agents/, skills/, and hooks/ directories.

What is the best way to organize plugin components for scalable Claude Code development?

The best way to organize plugin components for scalable Claude Code development is following the standardized blueprint with clear guidelines for naming, manifests, and component layout under dedicated directories to enable reliable auto-discovery.