Does Claude Code automatically find my plugin components?

Yes, Claude Code uses an auto-discovery mechanism that scans specific directories like /commands, /agents, and /skills for appropriately formatted files.

Where should I place my slash commands?

Slash commands should be placed in the /commands directory as Markdown files (.md) featuring specific YAML frontmatter.

How do I make my plugin paths portable?

Always use the ${CLAUDE_PLUGIN_ROOT} environment variable for internal file references to ensure the plugin works across different operating systems and installation methods.

What is the purpose of the .claude-plugin/ directory?

It holds the plugin.json manifest file, which is the required entry point for Claude Code to identify and configure your plugin.

Can I use custom directory names for my plugin components?

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

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Microck

byMicrock

•

Developer Tools

Standardizes and scaffolds the directory structure and manifest configuration for Claude Code plugins.

About

This skill provides comprehensive guidance on building and organizing Claude Code plugins using standardized directory layouts and manifest configurations. It helps developers correctly implement commands, agents, skills, and hooks while ensuring cross-platform portability through path resolution environment variables. Whether you are scaffolding a new plugin from scratch or reorganizing an existing project, this skill ensures your components are auto-discoverable and follow the official Claude Code architectural best practices.

Key Features

Portable path management using ${CLAUDE_PLUGIN_ROOT}
Manifest (plugin.json) schema and metadata validation
Automatic component discovery configuration and rules
81 GitHub stars
Standardized directory scaffolding for commands, agents, and skills
Event hook and MCP server integration patterns

Use Cases

Migrating hardcoded paths to portable environment variables for cross-platform support
Organizing complex plugins with multiple subagents, commands, and auto-activating skills
Scaffolding a new Claude Code plugin with a proper manifest and directory layout

About

Key Features

Portable path management using ${CLAUDE_PLUGIN_ROOT}
Manifest (plugin.json) schema and metadata validation
Automatic component discovery configuration and rules
81 GitHub stars
Standardized directory scaffolding for commands, agents, and skills
Event hook and MCP server integration patterns

Use Cases

Migrating hardcoded paths to portable environment variables for cross-platform support
Organizing complex plugins with multiple subagents, commands, and auto-activating skills
Scaffolding a new Claude Code plugin with a proper manifest and directory layout