Why is the ${CLAUDE_PLUGIN_ROOT} variable important?

It provides a portable way to reference files within your plugin, ensuring scripts and assets work regardless of the user's operating system or installation path.

What is the required structure for adding a new skill to a plugin?

Skills must be placed in individual subdirectories within the skills/ folder, each containing a mandatory SKILL.md file for identification.

How does Claude Code discover new slash commands?

Claude Code automatically scans the commands/ directory for Markdown files (.md) and loads them based on their YAML frontmatter configuration.

Where should the plugin manifest file be located?

The plugin.json manifest must be located within the .claude-plugin/ directory at the root of your plugin project.

Can I use custom directory names for my plugin components?

Yes, while there are default locations, you can specify custom relative paths for commands, agents, and hooks within the plugin.json manifest.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Microck

byMicrock

•

Developer Tools

Standardizes the creation and organization of Claude Code plugins through structured directory layouts and manifest configurations.

About

This skill provides comprehensive guidance for developers building Claude Code plugins, ensuring consistency and portability across different environments. It establishes a standardized directory hierarchy for commands, agents, and hooks while detailing the mandatory manifest definitions in plugin.json. By leveraging portable path references like ${CLAUDE_PLUGIN_ROOT} and following established naming conventions, this skill enables the development of maintainable, auto-discoverable extensions that integrate seamlessly with the Claude Code ecosystem.

Key Features

Auto-discovery setup for slash commands and subagents
Implementation of portable path references via ${CLAUDE_PLUGIN_ROOT}
89 GitHub stars
Automated directory scaffolding for commands, agents, and skills
Comprehensive manifest configuration for plugin.json metadata
Standardized naming conventions and component-based organization

Use Cases

Migrating local developer scripts into shareable, well-organized Claude Code plugins
Scaffolding a new Claude Code plugin with a portable and standard file structure
Configuring MCP servers within a plugin manifest for automated discovery

About

Key Features

Auto-discovery setup for slash commands and subagents
Implementation of portable path references via ${CLAUDE_PLUGIN_ROOT}
89 GitHub stars
Automated directory scaffolding for commands, agents, and skills
Comprehensive manifest configuration for plugin.json metadata
Standardized naming conventions and component-based organization

Use Cases

Migrating local developer scripts into shareable, well-organized Claude Code plugins
Scaffolding a new Claude Code plugin with a portable and standard file structure
Configuring MCP servers within a plugin manifest for automated discovery