Where should the plugin manifest be located?

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

What is the standard naming convention for plugin files?

All component directories and files should follow the kebab-case format (lowercase with hyphens) for consistency and cross-platform compatibility.

How does Claude Code discover new commands or skills?

Claude Code automatically scans the commands/, agents/, and skills/ directories at the plugin root level and registers any compatible markdown files or subdirectories.

How do I ensure my Claude Code plugin is portable?

Use the ${CLAUDE_PLUGIN_ROOT} environment variable for all internal path references in scripts, hooks, and MCP configurations instead of hardcoded paths.

Can I use custom directories for my plugin components?

Yes, you can specify custom paths for commands, agents, and hooks within the plugin.json manifest to supplement the default auto-discovery locations.

Claude Code Plugin Architecture

Name: Claude Code Plugin Architecture
Author: Microck

byMicrock

•

개발자 도구

Provides standardized patterns and directory layouts for building portable, auto-discoverable Claude Code plugins.

소개

This skill acts as a comprehensive architect for Claude Code extensions, guiding users through the essential directory structures, manifest configurations, and component organization required for professional plugin development. It ensures that plugins are built using best practices—such as kebab-case naming, manifest-driven discovery, and portable pathing using environment variables—allowing for seamless integration across different operating systems and installation methods. It is an indispensable resource for developers looking to scaffold new commands, subagents, or event hooks while maintaining a clean and maintainable codebase.

주요 기능

Portable path resolution using ${CLAUDE_PLUGIN_ROOT} variable
Standardized directory layout for automatic component discovery
89 GitHub stars
Detailed manifest configuration for .claude-plugin/plugin.json
Structured organization for commands, subagents, skills, and hooks
Model Context Protocol (MCP) server integration patterns

사용 사례

Refactoring an existing plugin to use portable pathing and auto-discovery
Scaffolding a new Claude Code plugin with a clean, standard structure
Configuring complex event-driven hooks and subagent hierarchies

소개

주요 기능

Portable path resolution using ${CLAUDE_PLUGIN_ROOT} variable
Standardized directory layout for automatic component discovery
89 GitHub stars
Detailed manifest configuration for .claude-plugin/plugin.json
Structured organization for commands, subagents, skills, and hooks
Model Context Protocol (MCP) server integration patterns

사용 사례

Refactoring an existing plugin to use portable pathing and auto-discovery
Scaffolding a new Claude Code plugin with a clean, standard structure
Configuring complex event-driven hooks and subagent hierarchies