Guide for organizing Claude Code plugin directories and creating manifests. Use when the user asks to "create plugin structure", "set up plugin directories", "plugin layout", "plugin manifest", or "plugin.json".
From claude-plugin-devnpx claudepluginhub nthplusio/functional-claude --plugin claude-plugin-devThis skill uses the workspace's default tool permissions.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Guide for organizing Claude Code plugin directories and manifests.
my-plugin/
├── .claude-plugin/
│ └── plugin.json # Required: manifest file
├── skills/ # SKILL.md in subdirectories
│ └── skill-name/
│ ├── SKILL.md
│ └── references/
├── agents/ # Agent definition files
│ └── agent-name.md
├── commands/ # Slash command definitions
│ └── command-name.md
├── hooks/
│ └── hooks.json # Event handlers
├── .mcp.json # MCP server configs
├── .lsp.json # LSP server configs
├── .local.example.md # Configuration template
├── .cache/ # Runtime cache (gitignored)
└── README.md
Critical: Only plugin.json goes inside .claude-plugin/. All other components go in the plugin root.
{
"name": "my-plugin",
"version": "1.0.0",
"description": "What this plugin does"
}
Optional fields: author (object with name/email), homepage, repository, license.
| Component | Convention | Example |
|---|---|---|
| Plugin name | kebab-case | code-reviewer |
| Skill name | Match directory | skill-name/SKILL.md |
| Agent name | Describe role | plugin-validator |
| Version | Semver | 1.0.0 |
Always include for runtime data:
.cache/
└── .gitignore # Contains: *
Use /create-plugin for an interactive workflow that guides through discovery, planning, implementation, validation, and documentation.
claude --plugin-dir ./my-plugin
Use the plugin-validator agent to check structure:
Validate my plugin at ./my-plugin