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

The .claude-plugin directory is a reserved folder that must contain the plugin.json manifest file, which is required for Claude Code to recognize and load the plugin.

Can I define custom paths for my plugin components?

Yes, while Claude Code has default directories, you can use the plugin.json manifest to specify custom relative paths for commands, agents, hooks, and MCP servers.

How does auto-discovery work in Claude Code?

Claude Code automatically scans root-level directories like /commands, /agents, and /skills for specific file types (like .md files with YAML frontmatter) and registers them without requiring manual configuration in the manifest.

Why is ${CLAUDE_PLUGIN_ROOT} important for plugin development?

It is an environment variable that provides a portable way to reference files within your plugin. Since plugins can be installed in different locations on different systems, using this variable prevents broken hardcoded paths.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: Microck

byMicrock

•

122

•

Developer Tools

Standardizes the creation and organization of Claude Code plugins using a structured directory layout and manifest configuration.

This skill provides a comprehensive blueprint for developing Claude Code plugins, ensuring seamless integration through automatic component discovery and standardized directory structures. It guides users through configuring the plugin.json manifest, organizing commands, agents, and skills, and implementing portable path references using ${CLAUDE_PLUGIN_ROOT} for robust, cross-platform compatibility. By following these architectural patterns, developers can build maintainable, portable, and easily discoverable extensions for the Claude Code ecosystem.

Key Features

01122 GitHub stars

02Component-based organization for commands, agents, skills, and hooks

03Naming conventions and best practices for professional plugin architecture

04Standardized directory layout for automatic component discovery

05Portable path resolution using the ${CLAUDE_PLUGIN_ROOT} variable

06Manifest-driven configuration for plugin metadata and custom paths

Use Cases

01Scaffolding a new Claude Code plugin from scratch with the correct folder hierarchy

02Converting a collection of standalone scripts into a structured, discoverable plugin

03Optimizing existing plugins for portability across different operating systems and environments

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add microck/ordinary-claude-skills command-name

For use in Claude.ai and ChatGPT

Download Skill