plugin-development

Create and organize Claude Code plugins with a standardized folder structure.

Updated Aug 27, 2026

Search Tags:#hooks #skills #agents #mcp #plugin #commands #claude-code

Ready to run

npx skills add https://github.com/ShunsukeHayashi/miyabi-claude-plugins --skill plugin-development-shunsukehayashi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-development
Source: https://github.com/ShunsukeHayashi/miyabi-claude-plugins/tree/main/miyabi-full/skills/plugin-development
Command: npx skills add https://github.com/ShunsukeHayashi/miyabi-claude-plugins --skill plugin-development-shunsukehayashi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers create and organize Claude Code plugins with a standardized structure that supports commands, skills, hooks, and agents, and aligns with MCP configuration.

Core Features & Use Cases

Standardized plugin layout: Clear folders for commands, skills, agents, hooks, and MCP config to ensure consistency across projects.
Extensibility: Simple paths to add new commands, skills, and agents without breaking existing plugins.
Documentation-friendly: Provides a single source of truth for plugin structure and guidance for onboarding new contributors.

Quick Start

Follow this guide to scaffold a new Claude Code plugin and begin implementing a command or skill.

Frequently Asked Questions about plugin-development

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

FAQPage Schema

How do I structure a Claude Code plugin to support commands, hooks, and agents?▼

Claude Code plugin development uses a standardized folder structure with separate directories for commands, skills, hooks, and agents to ensure project consistency. This layout supports extensibility and provides a single source of truth for onboarding contributors.

What is the standard directory layout for scaffolding a new Claude Code plugin?▼

The standard Claude Code plugin directory layout includes specific folders for commands, skills, agents, hooks, and MCP configuration, alongside optional resource directories like scripts/, references/, and assets/ to organize plugin resources effectively.

Can I configure MCP servers across multiple projects when developing a Claude Code plugin?▼

Yes, Claude Code plugin development covers MCP configuration across projects by defining server settings within the standardized plugin directory structure. This ensures consistent Model Context Protocol integration throughout your development workflow.

How do I add new commands and skills to an existing Claude Code plugin without breaking it?▼

You can add new commands and skills to an existing Claude Code plugin by placing them in their respective standardized folders. This extensible structure allows adding new features and agents without breaking existing plugin functionality.

Do I need a SKILL.md file to document my Claude Code plugin structure?▼

Yes, Claude Code plugin development requires a SKILL.md file with frontmatter containing a name and description. This satisfies the functional requirements and provides documentation-friendly guidance for plugin structure and contributor onboarding.

What's the best way to organize custom scripts and references within a Claude Code plugin?▼

The best way to organize custom scripts and references in a Claude Code plugin is using the optional resource directories like scripts/ and references/. These folders sit alongside the standardized commands, skills, hooks, and agents layout.