Can I use custom directory names for my plugin components?

Yes, while there are default locations, you can supplement them by specifying custom paths or arrays of paths within the plugin.json manifest.

Does Claude Code automatically find my commands?

Yes, Claude Code scans the commands/ directory at the plugin root for .md files and automatically registers them as slash commands.

What is the purpose of the hooks directory?

The hooks directory contains configuration (hooks.json) and scripts that allow the plugin to automatically respond to lifecycle events like SessionStart or PreToolUse.

What is the required location for the plugin manifest?

The plugin.json manifest must always be located within the .claude-plugin/ directory at the root of your plugin folder.

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

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

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Activer007

byActiver007

Developer Tools

Standardizes the creation, organization, and configuration of Claude Code plugins with best practices for manifests and component layouts.

About

The Claude Code Plugin Architect skill provides expert guidance on scaffolding and structuring Claude Code plugins to ensure seamless integration and maintainability. It helps developers master the mandatory directory patterns, manifest configurations in plugin.json, and the implementation of commands, agents, skills, and hooks. By emphasizing portable path references and automatic component discovery, this skill enables the creation of robust, cross-platform AI tools that follow Claude Code's native architecture standards.

Key Features

Applying naming conventions and component organization best practices
Scaffolding standardized Claude Code plugin directory structures
Implementing automatic discovery for commands, agents, and skills
Configuring plugin.json manifests with metadata and component paths
Managing portable paths using the ${CLAUDE_PLUGIN_ROOT} variable
0 GitHub stars

Use Cases

Refactoring existing AI tools into the standardized Claude Code component format
Bootstrapping a new Claude Code plugin from scratch with a valid manifest
Configuring cross-platform hooks and MCP server integrations within a plugin

About

Key Features

Applying naming conventions and component organization best practices
Scaffolding standardized Claude Code plugin directory structures
Implementing automatic discovery for commands, agents, and skills
Configuring plugin.json manifests with metadata and component paths
Managing portable paths using the ${CLAUDE_PLUGIN_ROOT} variable
0 GitHub stars

Use Cases

Refactoring existing AI tools into the standardized Claude Code component format
Bootstrapping a new Claude Code plugin from scratch with a valid manifest
Configuring cross-platform hooks and MCP server integrations within a plugin