plugin-structure

Guides creation of Claude Code plugin directory layouts, manifests, and component organization.

16|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SocialGouv/iterion --skill plugin-structure-socialgouv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/SocialGouv/iterion/tree/main/vendor/github.com/SocialGouv/claw-code-go/internal/tools/bundled_skills/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/SocialGouv/iterion --skill plugin-structure-socialgouv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers building Claude Code plugins often struggle with the required directory layout, plugin.json manifest fields, component auto-discovery rules, and portable path references, leading to plugins that fail to load or break across installations. ## Core Features & Use Cases - Directory Structure Guidance: Explains the standard plugin layout including .claude-plugin/, commands/, agents/, skills/, and hooks/ directories with auto-discovery rules. - Manifest Configuration: Documents every plugin.json field, path resolution rules, validation requirements, and minimal versus complete manifest examples. - Component Patterns: Provides organization patterns for commands, agents, skills, hooks, and scripts, plus three complete working examples from minimal to enterprise-grade. - Use Case: When scaffolding a new Claude Code plugin with slash commands, subagents, and hooks, use this Skill to set up plugin.json correctly, reference scripts with ${CLAUDE_PLUGIN_ROOT}, and troubleshoot components that fail to load. ## Quick Start Ask the AI to scaffold a new Claude Code plugin with a command, an agent, and a properly configured plugin.json manifest.

Frequently Asked Questions about plugin-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code plugin?▼

Create a directory containing .claude-plugin/plugin.json with at least a name field in kebab-case, then add component directories like commands/, agents/, or skills/ at the plugin root. Claude Code auto-discovers all .md files in these directories when the plugin is enabled.

What fields are required in plugin.json?▼

Only the name field is required, using kebab-case format unique across installed plugins. Recommended fields include version in semantic versioning format, description, author, homepage, repository, license, and keywords for discovery.

How do I reference files inside a Claude Code plugin?▼

Use the ${CLAUDE_PLUGIN_ROOT} environment variable for all intra-plugin paths in hooks, MCP server configs, and scripts. Never hardcode absolute paths or use home directory shortcuts, since plugins install in different locations across systems.

Why is my Claude Code plugin component not loading?▼

Components fail to load when files are in the wrong directory, have incorrect extensions, or contain invalid YAML frontmatter. Verify component directories sit at plugin root rather than inside .claude-plugin/, and confirm skills contain a SKILL.md file.

Can plugin.json specify custom component paths?▼

Yes, the commands, agents, hooks, and mcpServers fields accept custom paths that supplement default directories. Paths must be relative to plugin root, start with ./, and support arrays for multiple locations.