Where should the plugin manifest be located?

The plugin.json manifest must be placed within the .claude-plugin/ directory at the plugin root to be properly recognized.

Does Claude Code support auto-discovery of components?

Yes, Claude Code automatically scans standard directories like commands/, agents/, and skills/ for relevant markdown files and configurations.

What is the purpose of ${CLAUDE_PLUGIN_ROOT}?

It is a portable environment variable used to reference the plugin's root directory, ensuring paths work across different operating systems and installation methods.

Can I use custom paths for plugin components?

Yes, you can specify custom paths in the plugin.json manifest. Note that these supplement the default auto-discovery directories rather than replacing them.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Activer007

byActiver007

Developer Tools

Provides a standardized framework and scaffolding guidance for building well-organized, portable Claude Code plugins.

About

This skill serves as a comprehensive architectural guide for developers creating Claude Code plugins. It defines the mandatory directory layout, manifest configurations, and component organization—including commands, agents, skills, and hooks—necessary for seamless integration. By leveraging standardized patterns like the ${CLAUDE_PLUGIN_ROOT} variable and auto-discovery mechanisms, it ensures plugins remain portable and maintainable while following best practices for the Claude Code ecosystem.

Key Features

Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Component-based organization for commands, agents, and skills
Manifest (plugin.json) configuration and metadata guidance
0 GitHub stars
Standardized directory scaffolding and layout patterns
Auto-discovery mechanism implementation for seamless component loading

Use Cases

Migrating existing scripts or tools into a formal Claude Code plugin format
Scaffolding a new Claude Code plugin from scratch with the correct directory structure
Organizing complex plugins that require multiple specialized agents and automated hooks

About

Key Features

Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Component-based organization for commands, agents, and skills
Manifest (plugin.json) configuration and metadata guidance
0 GitHub stars
Standardized directory scaffolding and layout patterns
Auto-discovery mechanism implementation for seamless component loading

Use Cases

Migrating existing scripts or tools into a formal Claude Code plugin format
Scaffolding a new Claude Code plugin from scratch with the correct directory structure
Organizing complex plugins that require multiple specialized agents and automated hooks