plugin-structure

Name: plugin-structure
Availability: InStock
Author: jeffpecky

Document Claude Code plugin architecture, plugin.json, and directory structure.

Updated May 30, 2026

Search Tags:#claude code #plugin development #plugin architecture #component organization #auto-discovery

Ready to run

npx skills add https://github.com/jeffpecky/vortex --skill plugin-structure-jeffpecky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/jeffpecky/vortex/tree/main/src/vendor/official-plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/jeffpecky/vortex --skill plugin-structure-jeffpecky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and examples (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on Claude Code plugin architecture, helping developers create organized, maintainable plugins that integrate seamlessly with Claude Code.

Core Features & Use Cases

Plugin Architecture Overview: Learn about the directory structure and organization of Claude Code plugins.
Manifest Configuration: Understand how to set up and configure plugin.json.
Component Organization: Explore best practices for organizing commands, agents, skills, hooks, and MCP servers.
Auto-Discovery Mechanism: Learn how Claude Code automatically discovers and loads components.
Best Practices & Common Patterns: Get tips for organizing, naming, and maintaining plugins.
Use Case: Use this Skill to design and develop a new Claude Code plugin that automates routine tasks or provides specific functionality.

Quick Start

Run the plugin-structure skill to learn how to create a Claude Code plugin from scratch.

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

Structure your Claude Code plugin by organizing commands, agents, skills, hooks, and MCP servers into a standardized directory hierarchy. Configure the plugin.json manifest to enable seamless auto-discovery and loading by the Claude Code platform.

What is the plugin.json manifest used for in Claude Code?▼

The plugin.json manifest configures your Claude Code plugin's metadata and component organization. It defines how the platform integrates with your plugin and enables the auto-discovery mechanism for loading commands, agents, and hooks.

What's the best way to organize components in a Claude Code plugin?▼

Follow directory structure best practices by separating commands, agents, skills, hooks, and MCP servers into dedicated folders. Apply consistent naming conventions and component organization patterns to ensure maintainability and seamless platform auto-discovery.

Do I need prior plugin development experience to create a Claude Code plugin?▼

You need a basic understanding of plugin architecture and the Claude Code platform to build plugins. This resource provides comprehensive documentation, examples, and best practices to guide you through designing and implementing organized, maintainable plugins.

Why does my Claude Code plugin component organization matter?▼

Component organization directly affects the auto-discovery mechanism and platform integration. Properly structured commands, agents, skills, hooks, and MCP servers ensure Claude Code can automatically discover, load, and execute your plugin components without manual configuration.