plugin-structure

Define Claude Code plugin scaffolding with manifest and auto-discovery rules.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill plugin-structure-minhthang1009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill plugin-structure-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a clear, scalable template for building Claude Code plugins by standardizing directory layouts, manifests, and auto-discovery rules across commands, agents, and skills.

Core Features & Use Cases

  • Standard directory structure for plugin components (commands, agents, skills, hooks)
  • Clear plugin manifest guidance (.claude-plugin/plugin.json) and component path conventions
  • Guidance on auto-discovery, naming conventions, and portability for multi-environment deployments
  • Best-practice examples illustrating minimal and full-featured plugin setups

Quick Start

Create a new plugin folder with a .claude-plugin/plugin.json manifest and a skills/ directory containing a SKILL.md to describe the plugin structure.

Frequently Asked Questions about plugin-structure

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

FAQPage Schema
How do I structure a Claude Code plugin for auto-discovery of commands and agents?

To structure a Claude Code plugin for auto-discovery, define a standard directory layout with a .claude-plugin/plugin.json manifest and separate folders for commands, agents, and skills to enable automatic component loading.

What is the required manifest format for a Claude Code plugin?

The required manifest for a Claude Code plugin is a JSON file located at .claude-plugin/plugin.json, which defines essential metadata, component paths, and validation rules to ensure portability and proper auto-discovery.

How do I scaffold a scalable Claude Code plugin directory layout?

Scaffold a scalable Claude Code plugin by creating a root folder containing the .claude-plugin manifest alongside dedicated directories for commands, agents, skills, and hooks to enforce clear component separation and portability.

Does a Claude Code plugin require specific naming conventions for multi-environment deployments?

Yes, a Claude Code plugin requires specific naming conventions and path rules within the manifest to ensure components are correctly auto-discovered and maintain portability across multiple environments.

What are the limitations of not using a standard plugin structure in Claude Code?

Without a standard plugin structure, Claude Code cannot auto-discover commands, agents, or skills, leading to failed validation checks, broken portability, and maintenance issues during multi-environment deployments.