plugin-structure

Guide Claude Code plugin development with architecture and plugin.json structure.

2|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/koki3141/codex-global-skills --skill plugin-structure-koki3141
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/koki3141/codex-global-skills/tree/main/plugin-structure
Command: npx skills add https://github.com/koki3141/codex-global-skills --skill plugin-structure-koki3141

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a clear, structured approach to Claude Code plugin development, ensuring effective organization and maintainability.

Core Features & Use Cases

  • Plugin Architecture: Provides a detailed guide on Claude Code plugin architecture and directory layout.
  • Manifest Configuration: Explains plugin.json fields and best practices for manifest creation.
  • Component Organization: Outlines the organization patterns for commands, agents, skills, hooks, and scripts.
  • Auto-Discovery: Details the auto-discovery mechanism for components within Claude Code plugins.
  • Best Practices: Shares guidelines on organizing plugins, naming conventions, and portability.
  • Common Patterns: Includes examples of minimal, standard, and advanced plugins.
  • Troubleshooting: Offers solutions to common issues encountered during plugin development.
  • Use Cases: Ideal for developers seeking to create, organize, and maintain Claude Code plugins.

Quick Start

To create a new Claude Code plugin, navigate to the 'plugins' directory and use the following command:

claude /create-plugin "My Plugin Name"

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 maintainability?

Claude Code plugin architecture requires a root directory containing a plugin.json manifest and organized subdirectories for components like commands, agents, skills, hooks, and scripts. Auto-discovery mechanisms load these components during execution.

What fields do I need to configure in a Claude Code plugin.json manifest?

The plugin.json manifest requires specific fields to define plugin metadata and component configuration. Best practices include keeping manifests minimal, using standard naming conventions, and ensuring portability across different Claude Code environments.

What's the best way to organize commands, agents, and hooks in a Claude Code plugin?

Organize commands, agents, skills, hooks, and scripts into dedicated subdirectories within the plugin root. This separation leverages Claude Code's auto-discovery mechanism, ensuring each component type loads correctly and maintains structural separation.

Do I need Python and Bash to develop Claude Code plugins?

Python and Bash are required dependencies for executing scripts within Claude Code plugins. These runtime environments support automation, CI/CD integration, and infrastructure management tasks defined in the plugin's script components.

Why is my Claude Code plugin not auto-discovering components?

Auto-discovery issues in Claude Code plugins typically stem from incorrect directory organization or naming convention violations. Verify that component subdirectories match expected patterns and that the plugin.json manifest properly references all component locations.