How does Claude Code discover new skills or agents?

Claude Code uses an auto-discovery mechanism that automatically scans predefined directories like 'skills/' and 'agents/' whenever a plugin is enabled.

Can I use custom paths for my plugin components?

Yes, you can specify custom paths in the plugin.json manifest. These paths supplement the default directory structure rather than replacing it.

Where should I place my slash commands in a plugin?

Commands should be placed in a 'commands/' directory at the plugin root level as Markdown files (.md) with YAML frontmatter.

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

The .claude-plugin directory houses the mandatory plugin.json manifest, which defines the plugin's metadata and configuration for Claude Code.

What does the ${CLAUDE_PLUGIN_ROOT} variable do?

It is a dynamic environment variable used to reference the plugin's installation path, ensuring your scripts and hooks remain portable across different systems.

Claude Code Plugin Structure Guide

Name: Claude Code Plugin Structure Guide
Author: BbgnsurfTech

byBbgnsurfTech

•

Developer Tools

Provides a standardized framework for scaffolding and organizing Claude Code plugin components and manifest files.

About

This skill serves as a comprehensive architectural blueprint for developers creating Claude Code plugins. It provides expert guidance on directory layouts, manifest configuration in the .claude-plugin/plugin.json file, and the seamless integration of commands, agents, skills, and hooks. By utilizing this skill, developers can ensure their extensions follow official best practices for automatic discovery and portability, using standardized conventions like ${CLAUDE_PLUGIN_ROOT} to maintain compatibility across different operating systems and installation methods.

Key Features

Portable path management with ${CLAUDE_PLUGIN_ROOT}
Organization of commands, agents, and event hooks
Standardized directory layout scaffolding
Automatic component discovery patterns
Manifest (plugin.json) configuration guidance
3 GitHub stars

Use Cases

Scaffolding a new Claude Code plugin from scratch with the correct hierarchy
Configuring MCP servers and event handlers within a unified plugin structure
Refactoring existing local scripts into a portable, shareable plugin format

About

Key Features

Portable path management with ${CLAUDE_PLUGIN_ROOT}
Organization of commands, agents, and event hooks
Standardized directory layout scaffolding
Automatic component discovery patterns
Manifest (plugin.json) configuration guidance
3 GitHub stars

Use Cases

Scaffolding a new Claude Code plugin from scratch with the correct hierarchy
Configuring MCP servers and event handlers within a unified plugin structure
Refactoring existing local scripts into a portable, shareable plugin format