Plugin Structure FAQs

Question 1

Where should the plugin manifest file be located?

Accepted Answer

The 'plugin.json' manifest file must always be placed inside a directory named '.claude-plugin' at the root of your plugin folder. This file contains the essential metadata, such as the plugin name and version, required for Claude Code to recognize and initialize the extension.

Question 2

Can I use custom directory paths for my plugin components?

Accepted Answer

Yes. While Claude Code has default discovery paths, you can define custom locations for commands, agents, and hooks within the 'plugin.json' manifest. Note that custom paths supplement the default directories rather than replacing them, allowing for flexible organization.

Question 3

How does auto-discovery work in Claude Code?

Accepted Answer

Claude Code scans specific directories within your plugin root to automatically load functionality. For example, it looks for slash commands in 'commands/', subagents in 'agents/', and skills in 'skills/'. As long as you follow the standardized file structure, these components will register without manual configuration.

Question 4

What does the Plugin Structure skill do?

Accepted Answer

This skill provides a standardized blueprint for creating Claude Code plugins. It defines the required directory layout, manifest configuration (plugin.json), and naming conventions to ensure your custom tools, commands, and agents are automatically discovered and correctly integrated into Claude Code.

Question 5

Why is the ${CLAUDE_PLUGIN_ROOT} variable important?

Accepted Answer

The ${CLAUDE_PLUGIN_ROOT} variable is essential for portability. Because plugins can be installed via different methods (local, npm, marketplace) or on different operating systems, using this variable ensures that your internal file paths for scripts and assets remain valid regardless of the installation environment.

Plugin Structure

Plugin Structure

Key Features

Use Cases

Key Features

Use Cases