Can I use custom directory names for my commands or agents?

Yes, while there are default locations, you can specify custom paths in the plugin.json manifest to supplement the default auto-discovery directories.

Where should the plugin.json manifest be located?

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

How are commands discovered in a Claude Code plugin?

Claude Code automatically scans the commands/ directory for Markdown files with YAML frontmatter and registers them as slash commands.

What is the purpose of ${CLAUDE_PLUGIN_ROOT}?

It is an environment variable used for portable path references, ensuring your plugin works regardless of where the user installs it on their system.

What are the required fields in a plugin manifest?

The only strictly required field is 'name', which must be in kebab-case, though version and description are highly recommended for maintenance.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Microck

byMicrock

•

Developer Tools

Standardizes and scaffolds Claude Code plugin structures to ensure seamless integration and automatic component discovery.

About

This skill provides expert guidance on the architectural requirements for Claude Code plugins, covering everything from the mandatory .claude-plugin directory and manifest configuration to component-based organization of commands, agents, and hooks. It ensures developers follow best practices for naming conventions, portable path references using ${CLAUDE_PLUGIN_ROOT}, and auto-discovery mechanisms, enabling the creation of maintainable and professional-grade AI extensions that function reliably across different environments.

Key Features

Standardized directory layout for automatic component discovery
Detailed manifest (.plugin.json) configuration guidance
Best practices for naming conventions and component organization
Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Configuration patterns for hooks and MCP server integration
89 GitHub stars

Use Cases

Scaffolding a new Claude Code plugin from scratch with the correct hierarchy
Migrating existing scripts and tools into the standardized Claude Code plugin format
Troubleshooting plugin discovery issues and manifest configuration errors

About

Key Features

Standardized directory layout for automatic component discovery
Detailed manifest (.plugin.json) configuration guidance
Best practices for naming conventions and component organization
Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Configuration patterns for hooks and MCP server integration
89 GitHub stars

Use Cases

Scaffolding a new Claude Code plugin from scratch with the correct hierarchy
Migrating existing scripts and tools into the standardized Claude Code plugin format
Troubleshooting plugin discovery issues and manifest configuration errors