Plugin Structure

Scaffold Claude Code plugins with directory hierarchies and plugin.json manifests.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/dmedina-dev/dev-forge --skill plugin-structure-dmedina-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/dmedina-dev/dev-forge/tree/main/plugins/forge-plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/dmedina-dev/dev-forge --skill plugin-structure-dmedina-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill helps users who need to create, scaffold, or understand the structure of a Claude Code plugin, including manifest setup, component organization, and auto‑discovery configuration.

Core Features & Use Cases

  • Directory Layout Guidance: Shows the standard folder hierarchy (.claude-plugin, commands, agents, skills, hooks, scripts, etc.).
  • Manifest Configuration: Explains required fields in plugin.json and how to use ${CLAUDE_PLUGIN_ROOT} for portable paths.
  • Component Organization: Provides naming conventions and best‑practice tips for commands, agents, skills, hooks, and scripts.
  • Use Cases: Ideal when starting a new plugin, restructuring an existing one, or teaching others how to follow Claude Code architecture.

Quick Start

Guide me through scaffolding a new Claude Code plugin with the proper directory layout and manifest.

Frequently Asked Questions about Plugin Structure

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

FAQPage Schema
How do I scaffold a new Claude Code plugin with the proper directory layout?

Scaffolding a Claude Code plugin requires generating the standard directory hierarchy including .claude-plugin, commands, agents, skills, hooks, and scripts folders. This skill guides you through creating this structure and configuring auto-discovery for your components.

What is the correct structure for a plugin.json manifest file?

The plugin.json manifest defines your plugin's configuration and requires knowledge of specific fields and the ${CLAUDE_PLUGIN_ROOT} path variable. This skill explains the required manifest fields and how to use portable paths for component placement conventions.

Do I need to know the Claude Code architecture to create a plugin?

Yes, creating a Claude Code plugin requires knowledge of plugin.json structure, the ${CLAUDE_PLUGIN_ROOT} path variable, and component placement conventions. This skill is ideal for developers creating new plugins or reorganizing existing ones within the Claude ecosystem.

What's the best way to organize components like commands and hooks in a Claude plugin?

Organizing Claude plugin components requires following specific naming conventions and best-practice tips for commands, agents, skills, hooks, and scripts. The skill provides directory layout guidance and component organization rules to ensure proper auto-discovery configuration.

Can I use this skill to restructure an existing Claude Code plugin?

Yes, you can use this skill to reorganize existing plugins within the Claude ecosystem. It helps restructure your directory hierarchy, update your manifest configuration, and ensure your component organization follows current auto-discovery conventions.