How do I ensure my plugin paths are portable?

Always use the ${CLAUDE_PLUGIN_ROOT} environment variable for intra-plugin path references in your manifest and scripts to ensure they work across different installations.

Can I use custom directory names for my plugin components?

Yes, while there are default directories, you can specify custom paths for commands, agents, and hooks within the plugin.json file.

Does Claude Code automatically load my plugin components?

Yes, Claude Code uses an auto-discovery mechanism that scans specific directories like commands/, agents/, and skills/ for compatible files.

Where must the plugin manifest be located?

The plugin.json manifest MUST be located in the .claude-plugin/ directory at the root of your plugin.

What is the difference between a command and a skill?

Commands are user-invoked slash commands (e.g., /test), while skills are specialized capabilities that Claude Code autonomously activates based on task context.

Plugin Structure Guide

Name: Plugin Structure Guide
Author: arlenagreer

byarlenagreer

開発者ツール

Standardizes the creation and organization of Claude Code plugins using the SuperClaude framework conventions.

概要

This skill provides a definitive blueprint for building extensible Claude Code plugins, ensuring developers follow best practices for directory layout and component discovery. It provides comprehensive guidance on managing manifests, slash commands, specialized agents, and event hooks, allowing for the creation of portable and maintainable AI extensions. By leveraging the SuperClaude framework's auto-discovery mechanisms and the ${CLAUDE_PLUGIN_ROOT} variable, it streamlines the entire development lifecycle from initial scaffolding to final deployment.

主な機能

Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Manifest-driven configuration using standardized plugin.json schemas
Standardized naming conventions and directory layout best practices
Structured organization patterns for hooks and MCP server definitions
0 GitHub stars
Automated component discovery for commands, agents, and skills

ユースケース

Scaffolding a new Claude Code plugin from scratch with the correct directory tree
Organizing existing scripts and tools into a modular plugin architecture
Configuring event hooks and MCP servers for deep Claude Code integration

概要

主な機能

Portable path management using the ${CLAUDE_PLUGIN_ROOT} variable
Manifest-driven configuration using standardized plugin.json schemas
Standardized naming conventions and directory layout best practices
Structured organization patterns for hooks and MCP server definitions
0 GitHub stars
Automated component discovery for commands, agents, and skills

ユースケース

Scaffolding a new Claude Code plugin from scratch with the correct directory tree
Organizing existing scripts and tools into a modular plugin architecture
Configuring event hooks and MCP servers for deep Claude Code integration