From plugin-dev
Guides developers on Claude Code plugin development, covering architecture, components, and routing to 9 specialized skills for tasks like structure, commands, agents, and LSP integration.
npx claudepluginhub sjnims/plugin-dev --plugin plugin-devThis skill uses the workspace's default tool permissions.
This meta-skill provides an overview of Claude Code plugin development and routes to specialized skills based on the task at hand.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
This meta-skill provides an overview of Claude Code plugin development and routes to specialized skills based on the task at hand.
The plugin-dev toolkit provides 9 specialized skills for building Claude Code plugins, plus this guide. Each skill handles a specific domain of plugin development.
| Skill | Purpose |
|---|---|
| plugin-structure | Directory layout, manifest, component organization |
| command-development | Simple prompts (single .md files in commands/) |
| agent-development | Autonomous subagents |
| skill-development | Complex prompts with bundled resources (skills/) |
| hook-development | Event-driven automation |
| mcp-integration | Model Context Protocol servers |
| lsp-integration | Language Server Protocol for code intelligence |
| plugin-settings | User configuration via .local.md |
| marketplace-structure | Plugin marketplace creation |
Skill: plugin-structure
Use when the user needs to:
Skill: command-development
Use when the user needs to:
[BANG] backticksSkill: agent-development
Use when the user needs to:
Skill: skill-development
Use when the user needs to:
Skill: hook-development
Use when the user needs to:
Skill: mcp-integration
Use when the user needs to:
Skill: lsp-integration
Use when the user needs to:
Skill: plugin-settings
Use when the user needs to:
Skill: marketplace-structure
Use when the user needs to:
User wants to...
├── Create/organize a plugin structure? → plugin-structure
├── Add a simple slash command (no bundled resources)? → command-development
├── Create an autonomous agent? → agent-development
├── Add a complex skill with scripts/references? → skill-development
├── React to Claude Code events? → hook-development
├── Integrate external service/API? → mcp-integration
├── Add code intelligence/LSP? → lsp-integration
├── Make plugin configurable? → plugin-settings
└── Distribute multiple plugins? → marketplace-structure
plugin-structure skill to create directory layoutcommand-development for user-facing commandshook-development for event-driven behaviorplugin-settings if user configuration neededplugin-structure for basic structuremcp-integration to configure MCP serverscommand-development to create commands that use MCP toolsagent-development for autonomous MCP workflowsplugin-structure for basic structurelsp-integration to configure language serverscommand-development for commands using LSP featuresplugin-structure for basic structureskill-development to create specialized skillsThe plugin-dev plugin also provides 3 agents:
| Agent | Purpose |
|---|---|
| plugin-validator | Validates plugin structure and manifests |
| skill-reviewer | Reviews skill quality and triggering |
| agent-creator | Generates new agents from descriptions |
Use agents proactively after creating components to ensure quality.
| Command | Purpose |
|---|---|
/plugin-dev:plugin-dev-guide | Overview and skill routing |
/plugin-dev:start | Entry point - choose plugin or marketplace creation |
/plugin-dev:create-plugin | 8-phase guided plugin creation workflow |
/plugin-dev:create-marketplace | 8-phase guided marketplace creation workflow |
$ARGUMENTS
If the user provided a request above, analyze it and either:
If no request was provided, summarize the available plugin development capabilities and ask what the user wants to build or learn about.