plugin-structure

Organize Claude Code plugin directories with manifests and portable references.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Wizarck/eligia-skills --skill plugin-structure-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/Wizarck/eligia-skills/tree/main/claude-plugins-official/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/Wizarck/eligia-skills --skill plugin-structure-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you design and maintain a predictable Claude Code plugin layout so skills, commands, agents, hooks, and supporting files are discovered correctly without fragile ad hoc organization.

Core Features & Use Cases

  • Plugin directory design: Clarifies where manifests, component folders, and shared resources belong in a plugin root.
  • Manifest configuration: Explains how to define plugin metadata and custom component paths in plugin.json.
  • Portable references: Shows how to use ${CLAUDE_PLUGIN_ROOT} and relative paths so plugins work across environments.
  • Use case: Use it when scaffolding a new plugin, reorganizing an existing plugin, or troubleshooting why components are not loading.

Quick Start

Ask the assistant to scaffold a Claude Code plugin directory with the correct manifest, skill folders, and component layout.

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

To structure a Claude Code plugin directory for auto-discovery, create a root-level `.claude-plugin/plugin.json` manifest and organize component folders for commands, agents, skills, hooks, and MCP server resources using kebab-case naming conventions.

Why are my Claude Code plugin components not loading correctly?

Plugin components fail to load correctly when the directory layout lacks the required root-level `.claude-plugin/plugin.json` manifest, uses non-standard naming conventions, or omits relative `./` paths for component discovery.

How does path resolution work for portable Claude Code plugin references?

Portable Claude Code plugin path resolution uses the `${CLAUDE_PLUGIN_ROOT}` variable and relative `./` paths to ensure component references work predictably across different deployment environments without hardcoding absolute file locations.

What is the best way to scaffold a maintainable Claude Code plugin layout?

The best way to scaffold a maintainable Claude Code plugin layout is arranging manifests, component folders, and shared resources in the plugin root to ensure skills, commands, agents, and hooks are discovered correctly without fragile ad hoc organization.

Can I configure custom component paths in a Claude Code plugin manifest?

Yes, you can configure custom component paths in a Claude Code plugin manifest by defining plugin metadata and directory routing rules inside the root-level `plugin.json` file to guide the auto-discovery mechanism.

When do I need a root-level plugin.json manifest for my Claude Code plugin?

You need a root-level `plugin.json` manifest whenever you scaffold a new Claude Code plugin, reorganize existing component folders, or troubleshoot loading issues to ensure the auto-discovery system correctly identifies and registers your components.