skills.rest
EmaRimoldi
EmaRimoldiCOMMUNITY
Explore all skills by this author →
GitHub

plugin-structure

Design Claude Code plugin structures with manifest placement and component organization.

Updated Mar 27, 2026
Search Tags:#architecture#discovery#manifest#best-practices#kebab-case#claude-code#plugin-structure
One-click install
npx skills add https://github.com/EmaRimoldi/Claude-scholar-extended --skill plugin-structure-emarimoldi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/EmaRimoldi/Claude-scholar-extended/tree/main/skills/plugin-structure
Command: npx skills add https://github.com/EmaRimoldi/Claude-scholar-extended --skill plugin-structure-emarimoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, practical guide to designing Claude Code plugin structures, including manifest placement, component organization, and auto-discovery rules, to reduce setup time and errors.

Core Features & Use Cases

  • Explains the required plugin root layout, including .claude-plugin/plugin.json, and the standard directories for commands, agents, skills, hooks, MCP servers, and optional resources.
  • Demonstrates naming conventions (kebab-case), portably referencing ${CLAUDE_PLUGIN_ROOT}, and how to extend with custom paths.
  • Use cases include scaffolding a new plugin, auditing an existing plugin, and debugging component discovery issues.

Quick Start

Create a minimal plugin structure and verify auto-discovery in Claude Code.

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 correct auto-discovery?▼

A minimal Claude Code plugin structure requires a manifest at .claude-plugin/plugin.json alongside standard directories for commands, agents, skills, hooks, and MCP servers to enable auto-discovery.

What naming conventions does Claude Code plugin structure require?▼

Claude Code plugin structure enforces kebab-case naming conventions for files and directories to ensure compatibility, alongside portably referencing paths using the ${CLAUDE_PLUGIN_ROOT} variable.

Does Claude Code plugin structure require a plugin.json manifest?▼

Yes, a plugin.json manifest is strictly required for Claude Code plugin structure and must be placed inside the .claude-plugin directory at the project root to validate the plugin.

Why is my Claude Code plugin component discovery not working?▼

Claude Code plugin component discovery fails when the structure lacks the .claude-plugin/plugin.json manifest, violates kebab-case naming, or omits standard directories for commands, agents, and hooks.

Can I add custom directories to a Claude Code plugin structure?▼

Yes, you can extend the Claude Code plugin structure with custom paths and optional resources directories alongside the standard component folders for commands, agents, skills, hooks, and MCP servers.

Related Skills

Explore More Software Engineering Skills→
ecielamecielam

Plugin Structure

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

Community
Intermediate
tzachbontzachbon
432

Plugin Structure

Design and validate Claude Code plugin directory structures and manifests.

Community
Intermediate
open-sessionopen-session

Plugin Structure

Organize Claude Code plugin components with portable manifest paths.

Official
Advanced
Delqhi-ProjectsDelqhi-Projects
3

Plugin Structure

Scaffold Claude Code plugin structures with manifest configuration and auto-discovery.

Official
Advanced