Plugin Structure

Structure Claude Code plugins with plugin.json manifests and portable path references.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill plugin-structure-susomejias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/susomejias/rembric --skill plugin-structure-susomejias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and common errors developers face when building Claude Code plugins, ensuring they follow official conventions for automatic component discovery, cross-platform portability, and long-term maintainability without broken paths or misconfigured manifests.

Core Features & Use Cases

  • Complete Plugin Structure Guidance: Covers directory layout, plugin.json manifest configuration, and organization of all component types (commands, agents, skills, hooks) for Claude Code plugins.
  • Best Practices & Troubleshooting: Provides actionable rules for portable path references using ${CLAUDE_PLUGIN_ROOT}, kebab-case naming conventions, and solutions for common issues like auto-discovery failures and path resolution errors.
  • Use Case: A developer building a team-wide code review plugin can use this Skill to correctly structure all components, configure the manifest, and avoid path errors that would prevent the plugin from loading in Claude Code.

Quick Start

Use the Plugin Structure skill to scaffold a new Claude Code plugin with the correct directory layout and manifest configuration for your team's internal developer tools.

Frequently Asked Questions about Plugin Structure

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

FAQPage Schema
Why does my Claude Code plugin fail to load components?

Claude Code plugin auto-discovery failures usually stem from incorrect directory layout, missing plugin.json manifest configuration, or improper component organization that violates standard naming conventions.

How do I use portable paths in Claude Code plugin development?

Use the ${CLAUDE_PLUGIN_ROOT} variable for portable path references in your Claude Code plugin to ensure cross-platform compatibility and prevent broken paths during component resolution.

What is the correct naming convention for Claude Code plugin components?

The correct naming convention for Claude Code plugin components is kebab-case, ensuring compliant plugin manifests and reliable auto-discovery across different operating systems.

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

The best way to configure a plugin.json manifest for Claude Code is to follow official conventions for component organization, ensuring all commands, agents, and hooks are properly declared for maintainability.

Can I use Claude Code plugins across different operating systems without path errors?

Yes, you can achieve cross-platform plugin compatibility in Claude Code by implementing portable path references with ${CLAUDE_PLUGIN_ROOT} and adhering to the official directory layout design.