developing-claude-code-plugins

Developing Claude Code plugins involves planning structure, implementing functionality, testing components, and distributing through the marketplace. This Skill provides workflow templates and practical examples guiding the full lifecycle from scaffolding to release, including manifest formats, resource patterns, and distribution steps.

Claude Code plugins follow established patterns for common scenarios: simple skills, MCP server integration, command collections, and full-featured plugins. Pattern guidance in this Skill covers plugin structure, component wiring, hook implementation, and cross-component workflows to ensure consistency and maintainability.

Testing Claude Code plugins requires structured workflows for validating functionality across scaffolded components and integrated resources. This Skill includes debugging strategies, testing patterns, and practical examples demonstrating how to verify hooks, commands, agents, and MCP server behavior before marketplace release.

Claude Code plugins must satisfy functional and technical requirements including proper manifest formats, resource bundling, component structure, and marketplace distribution criteria. This Skill provides specifications for plugin structure, configuration formats, and release checklists ensuring compliance before submission.

Yes, Claude Code plugins support MCP server integration, command collections, and external agent wiring. This Skill covers guidance for hooks, MCP server patterns, command structures, and cross-component workflows needed to bundle these capabilities into a cohesive plugin.

Scaffolding a Claude Code plugin starts with structured planning and component organization following established patterns. This Skill provides workflow templates for project setup, resource layout, manifest configuration, and directory structures that accelerate development and ensure marketplace-ready output.