plugin-structure

Document Claude Code plugin architecture, directory layout, and manifest configuration.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/spandios/vibe-utils --skill plugin-structure-spandios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/spandios/vibe-utils/tree/main/skills/plugin-structure
Command: npx skills add https://github.com/spandios/vibe-utils --skill plugin-structure-spandios

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive guidance on structuring, organizing, and configuring Claude Code plugins, ensuring seamless integration and discoverability.

Core Features & Use Cases

  • Directory Structure: Understand the conventional layout for automatic discovery.
  • Manifest Configuration: Learn to set up plugin.json with essential metadata and paths.
  • Component Organization: Best practices for commands, agents, skills, and hooks.
  • Portable Paths: Master the use of ${CLAUDE_PLUGIN_ROOT} for robust plugin development.
  • Use Case: When starting a new plugin project, use this Skill to set up the correct directory structure and configure the plugin.json manifest for optimal discoverability and functionality.

Quick Start

Use the plugin-structure skill to understand how to organize plugin components.

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 automatic component discovery?

Structure your Claude Code plugin using a conventional directory layout that enables automatic discovery of components like commands, agents, skills, and hooks without manual configuration.

What is the correct directory layout for Claude Code plugin development?

The correct directory layout organizes components into specific folders for commands, agents, skills, and hooks, ensuring seamless integration and maintainability across the plugin architecture.

How do I configure plugin.json manifest metadata for a Claude Code plugin?

Configure the plugin.json manifest by defining essential metadata and paths to set up your Claude Code plugin for optimal functionality and discoverability within the system.

How does the portable path variable work in Claude Code plugin architecture?

The portable path variable `${CLAUDE_PLUGIN_ROOT}` works by providing robust, relative path references within your plugin, ensuring your components remain location-independent and maintainable.

Can I organize custom hooks and agents within a single Claude Code plugin?

Yes, you can organize custom hooks and agents within a single Claude Code plugin by following best practices for component organization to ensure they are properly discoverable.

What are the limitations of manual plugin configuration versus auto-discovery in Claude Code?

Manual plugin configuration limitations include potential path misalignments and poor maintainability, whereas the auto-discovery mechanism relies on a strict conventional directory structure to function correctly.