plugin-structure

Name: plugin-structure
Availability: InStock
Author: DMT123

Guide Claude Code plugin architecture with directory structure and plugin.json configuration.

Updated Mar 2, 2026

Search Tags:#architecture #best practices #claude code #plugin development #component organization #manifest configuration

Ready to run

npx skills add https://github.com/DMT123/claude-skills-collection --skill plugin-structure-dmt123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/DMT123/claude-skills-collection/tree/main/plugins/plugin-dev/plugin-structure
Command: npx skills add https://github.com/DMT123/claude-skills-collection --skill plugin-structure-dmt123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on building and organizing Claude Code plugins, ensuring adherence to best practices and efficient component management.

Core Features & Use Cases

Plugin Architecture: Understand directory structure, manifest configuration, and component organization.
Component Management: Learn how to structure commands, agents, skills, and hooks.
Use Case: When starting a new plugin project, use this Skill to understand the recommended directory layout, how to configure plugin.json, and best practices for naming conventions and auto-discovery.

Quick Start

Use the plugin-structure skill to understand how to organize a new Claude Code plugin.

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

To structure a Claude Code plugin directory, organize components like commands, agents, skills, and hooks into a logical hierarchy, then configure the `plugin.json` manifest to enable auto-discovery and portable path references.

What is the best way to configure a plugin.json manifest for Claude Code?▼

Configuring a `plugin.json` manifest involves defining the schema for your Claude Code plugin, specifying component organization, and applying naming conventions to ensure proper auto-discovery and integration of commands and hooks.

How do I organize components like agents, skills, and hooks in Claude Code plugin development?▼

Organize Claude Code plugin components by placing commands, agents, skills, and hooks into dedicated directories, adhering to file naming conventions and best practices for architecture to ensure efficient component management.

Does Claude Code plugin architecture support portable path references for cross-environment deployment?▼

Yes, Claude Code plugin architecture supports portable path references, allowing developers to define file locations in the `plugin.json` manifest that resolve correctly across different deployment environments.

When do I need to use specific file naming conventions in Claude Code plugin development?▼

You need specific file naming conventions during Claude Code plugin development to enable the framework's auto-discovery mechanism to correctly identify and load commands, agents, skills, and hooks from your directory structure.

Why does my Claude Code plugin fail to auto-discover custom hooks?▼

Auto-discovery of custom hooks fails when the directory structure or file naming conventions do not match the expected `plugin.json` schema, preventing the Claude Code architecture from properly identifying components.