What is the purpose of ${CLAUDE_PLUGIN_ROOT}?

It is a portable environment variable used for intra-plugin path references, ensuring your plugin works across different operating systems and installation paths.

Can I define custom paths for my plugin commands?

Yes, you can specify custom paths or arrays of paths in the 'commands' field of your plugin.json manifest to supplement default locations.

Where should the plugin.json file be located?

The manifest MUST be located in the .claude-plugin/ directory at the root of your plugin to be recognized by Claude Code.

Does Claude Code automatically load my plugin components?

Yes, Claude scans the commands/, agents/, and skills/ directories automatically for markdown and configuration files unless overridden in the manifest.

Claude Code Plugin Architecture

Name: Claude Code Plugin Architecture
Author: Activer007

byActiver007

Developer Tools

Standardizes the directory layout and manifest configuration for building well-organized Claude Code plugins.

About

This skill provides a comprehensive blueprint for organizing Claude Code plugins, ensuring seamless integration through automatic component discovery and manifest-driven configuration. It guides developers through the mandatory directory structures, the correct setup of the .claude-plugin/plugin.json manifest, and the implementation of commands, agents, and skills. By enforcing best practices like portable path references via ${CLAUDE_PLUGIN_ROOT} and naming conventions, it enables the creation of maintainable, cross-platform plugins that extend Claude's core capabilities.

Key Features

0 GitHub stars
Automatic component discovery for commands and agents
Best practices for naming conventions and versioning
Portable path referencing using ${CLAUDE_PLUGIN_ROOT}
Standardized directory layout for skills and hooks
Manifest configuration for plugin metadata and overrides

Use Cases

Configuring MCP servers and event hooks within a plugin manifest
Scaffolding a new Claude Code plugin from scratch
Restructuring existing utilities into a standardized plugin format

About

Key Features

0 GitHub stars
Automatic component discovery for commands and agents
Best practices for naming conventions and versioning
Portable path referencing using ${CLAUDE_PLUGIN_ROOT}
Standardized directory layout for skills and hooks
Manifest configuration for plugin metadata and overrides

Use Cases

Configuring MCP servers and event hooks within a plugin manifest
Scaffolding a new Claude Code plugin from scratch
Restructuring existing utilities into a standardized plugin format