skills.rest
murphyjoseph
murphyjosephCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plugin-structure

Scaffold Claude Code plugins with standardized directory layouts and plugin.json manifests.

Updated Mar 1, 2026
Search Tags:#architecture#skills#plugin#manifest#commands#claude-code#auto-discovery
One-click install
npx skills add https://github.com/murphyjoseph/dojo-kit --skill plugin-structure-murphyjoseph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/murphyjoseph/dojo-kit/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/murphyjoseph/dojo-kit --skill plugin-structure-murphyjoseph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of building Claude Code plugins that adhere to a standardized, scalable architecture, including manifest placement, component organization, and auto-discovery conventions.

Core Features & Use Cases

  • Clear guidance on the conventional directory layout (commands, agents, skills, hooks) and optional resources (scripts, references, assets)
  • Instructions for configuring and validating the plugin manifest (plugin.json) and custom paths
  • Detailed explanation of auto-discovery, portable path references using ${CLAUDE_PLUGIN_ROOT}, and component loading order
  • Best practices for maintainability, naming, and documentation to support large, reusable plugin ecosystems
  • Use cases include scaffolding new plugins, organizing complex projects, and aligning team conventions

Quick Start

Create a new plugin directory named your-plugin, place a .claude-plugin/plugin.json manifest at the root, and implement standard directories for commands, agents, skills, hooks, and optional resources following the plugin-structure.

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 manifest and directory layout?▼

Auto-discovery for Claude Code plugins works by scanning standard root directories for commands, agents, skills, and hooks. You configure it by placing components in their designated folders and validating paths using the `${CLAUDE_PLUGIN_ROOT}` variable in the manifest.

What is the conventional folder organization for Claude Code commands and hooks?▼

The conventional folder organization for Claude Code separates components into default directories for commands, agents, skills, and hooks. You can also add optional resources directories like scripts, references, and assets to support large, reusable plugin ecosystems.

Can I use custom paths for Claude Code plugin components and resources?▼

To scaffold a new Claude Code plugin, create a directory named your-plugin, place the `.claude-plugin/plugin.json` manifest at the root, and implement standard directories for commands, agents, skills, and hooks following the plugin-structure guidelines.

When do I need a standardized plugin architecture for Claude Code projects?▼

The best practice for maintaining large Claude Code plugins is adhering to a standardized directory layout, using portable path references like `${CLAUDE_PLUGIN_ROOT}`, and following naming and documentation conventions to support reusable plugin ecosystems.

Related Skills

Explore More Software Engineering Skills→
ecielamecielam

Plugin Structure

Scaffold Claude Code plugins with standardized directory structures and manifest configuration.

Community
Intermediate
NGTPTENGTPTE

plugin-structure

Structure Claude Code plugin directories and manifests for reliable component discovery.

Community
Advanced
Kilo-OrgKilo-Org
166

skill-creator

Scaffold SKILL.md frontmatter and starter directories for new skills.

Official
Intermediate
phillip-hirschphillip-hirsch

plugin-structure

Explain Claude Code plugin architecture, directory layout, and component organization.

Community
Advanced