Plugin Structure

Generate a starter Claude Code plugin skeleton with standard directory layout.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/stevessr/dotsfiles --skill plugin-structure-stevessr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/stevessr/dotsfiles/tree/main/dot_claude/private_plugins/private_marketplaces/claude-code-plugins/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/stevessr/dotsfiles --skill plugin-structure-stevessr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding and applying Claude Code plugin architecture can be confusing without a clear, structured guide. This section helps teams adopt a consistent plugin layout, manifest conventions, and auto-discovery rules.

Core Features & Use Cases

  • Clarifies standard directory layout (commands/, agents/, skills/, hooks/), manifest placement, and auto-discovery behavior.
  • Demonstrates best practices for portable references using ${CLAUDE_PLUGIN_ROOT} and kebab-case naming.
  • Use cases include scaffolding a new plugin, organizing components, and validating plugin structure during onboarding.

Quick Start

Generate a starter Claude Code plugin skeleton following the official Plugin Structure guidelines.

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

Use standard directories like commands/, agents/, skills/, and hooks/ for component layout. Place a SKILL.md file at the plugin root with YAML frontmatter including name, description, and version to enable proper auto-discovery.

What is the required manifest configuration for a Claude Code plugin?

The manifest configuration requires YAML frontmatter in the SKILL.md file specifying the plugin name, description, and version. This ensures proper component layout validation and auto-discovery behavior.

How do I scaffold a new Claude Code plugin skeleton?

Scaffold a Claude Code plugin by creating a root directory containing a SKILL.md file with required YAML frontmatter. Add optional resource directories like scripts/, references/, and assets/ to organize supporting files.

Can I use portable references in Claude Code plugin development?

Yes, use portable references in Claude Code plugin development by utilizing the ${CLAUDE_PLUGIN_ROOT} variable. This ensures file paths remain consistent across different environments and standardizes component layout.

What naming convention should I use for Claude Code plugin components?

Use kebab-case naming for Claude Code plugin components to maintain consistency and avoid discovery conflicts. This standardizes component layout across commands/, agents/, skills/, and hooks/ directories.

What are the limitations of Claude Code plugin auto-discovery?

Auto-discovery limitations require strict adherence to the standard directory layout and manifest placement. If the SKILL.md is missing from the skill root or lacks proper YAML frontmatter, the plugin will not be discovered.