How does Claude Code discover new commands or agents?

Claude Code uses an auto-discovery mechanism that scans specific directories like commands/, agents/, and skills/ for valid markdown files with appropriate frontmatter.

Where should the plugin manifest be located?

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

What is the benefit of using ${CLAUDE_PLUGIN_ROOT}?

It ensures your plugin remains portable across different operating systems and installation methods by providing a dynamic reference to the plugin's base directory.

Can I use custom directory names for my components?

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

What naming convention should I use for plugin files?

Standard practice is to use kebab-case (lowercase with hyphens) for all directory and file names to ensure consistency and system compatibility.

Plugin Structure Guide

Name: Plugin Structure Guide
Author: nordeim

bynordeim

Learning & Documentation

Standardizes the development and organization of Claude Code plugins through conventional directory layouts and manifest configurations.

About

This skill provides comprehensive architectural guidance for developers building Claude Code plugins, ensuring seamless integration through standardized directory structures and automatic component discovery. It covers essential topics including manifest configuration in .claude-plugin/plugin.json, component-based organization for commands and agents, and the use of the ${CLAUDE_PLUGIN_ROOT} environment variable for creating portable, cross-platform extensions. By following these established patterns, developers can build maintainable, scalable, and professional-grade plugins that leverage Claude Code's full automation capabilities.

Key Features

Automatic component discovery patterns
Standardized directory layout for commands, agents, and skills
0 GitHub stars
Manifest (plugin.json) configuration standards
Cross-platform path resolution using ${CLAUDE_PLUGIN_ROOT}
Component-specific file naming and organization conventions

Use Cases

Scaffolding a new Claude Code plugin from scratch
Implementing portable path references for multi-OS support
Refactoring an existing plugin to follow standard architecture

About

Key Features

Automatic component discovery patterns
Standardized directory layout for commands, agents, and skills
0 GitHub stars
Manifest (plugin.json) configuration standards
Cross-platform path resolution using ${CLAUDE_PLUGIN_ROOT}
Component-specific file naming and organization conventions

Use Cases

Scaffolding a new Claude Code plugin from scratch
Implementing portable path references for multi-OS support
Refactoring an existing plugin to follow standard architecture