Where should the plugin manifest be located?

The plugin.json manifest must be placed within the .claude-plugin/ directory at the root of your plugin to be recognized by Claude Code.

Does Claude Code automatically find my plugin commands?

Yes, Claude Code uses an auto-discovery mechanism that automatically scans the commands/, agents/, and skills/ directories at the plugin root.

What components can I include in a Claude Code plugin?

Plugins can include slash commands, specialized subagents, auto-activating skills, event hooks (JSON), and MCP server definitions.

How do I ensure my plugin works on different operating systems?

Use the ${CLAUDE_PLUGIN_ROOT} environment variable for all internal path references instead of hardcoded absolute or relative paths.

What naming convention should I use for plugin files?

It is best practice to use kebab-case (lowercase with hyphens) for all directory names and component files to ensure broad compatibility.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Microck

byMicrock

•

Herramientas para Desarrolladores

Guides developers through scaffolding, organizing, and configuring standardized Claude Code plugin architectures and manifests.

Acerca de

This skill provides comprehensive guidance on building Claude Code plugins using standardized directory structures and industry best practices. It helps developers set up manifest files, organize components like commands and agents, implement hooks, and ensure portability using system variables. Whether you're scaffolding a new plugin from scratch or refactoring an existing project, this skill ensures your architecture follows the official auto-discovery patterns and naming conventions for seamless integration with the Claude Code environment.

Características Principales

Scaffold standardized directory layouts for commands, agents, and skills
89 GitHub stars
Configure plugin.json manifests with required and recommended metadata
Implement portable path references using ${CLAUDE_PLUGIN_ROOT}
Set up event-driven hooks and MCP server definitions
Optimize component organization for Claude Code's automatic discovery mechanism

Casos de Uso

Creating a new Claude Code plugin from scratch with the correct file hierarchy
Migrating hardcoded paths to portable environment variables for cross-platform support
Configuring complex manifests with custom component paths and auto-discovery overrides

Acerca de

Características Principales

Scaffold standardized directory layouts for commands, agents, and skills
89 GitHub stars
Configure plugin.json manifests with required and recommended metadata
Implement portable path references using ${CLAUDE_PLUGIN_ROOT}
Set up event-driven hooks and MCP server definitions
Optimize component organization for Claude Code's automatic discovery mechanism

Casos de Uso

Creating a new Claude Code plugin from scratch with the correct file hierarchy
Migrating hardcoded paths to portable environment variables for cross-platform support
Configuring complex manifests with custom component paths and auto-discovery overrides