plugin-structure

Name: plugin-structure
Availability: InStock
Author: pixl

Scaffold and organize Claude Code plugins with directory layout and manifest configuration.

2|Updated Mar 16, 2026

Search Tags:#scaffold #plugin #manifest #claude-code #auto-discovery #directory-structure

Ready to run

npx skills add https://github.com/hamzaPixl/pixl-ai --skill plugin-structure-hamzapixl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/plugin-structure
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill plugin-structure-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers need clear guidance to create, audit, and maintain Claude Code plugins with a consistent directory layout, manifest configuration, and auto‑discovery of components.

Core Features & Use Cases

Directory Layout Guidance: Standardized folders for commands, agents, skills, hooks, and scripts.
Manifest Management: Detailed plugin.json fields, validation rules, and best‑practice examples.
Component Organization: Patterns for commands, agents, skills, hooks, and scripts, including naming conventions.
Portable Paths: Use of ${CLAUDE_PLUGIN_ROOT} for reliable cross‑environment references.
Progressive Disclosure: Core concepts in SKILL.md, with deep references and examples loaded on demand.
Related Skills: Works with hook‑development and marketplace‑publishing for full plugin lifecycle.

Quick Start

Use the plugin‑structure skill to generate a complete plugin scaffold with a manifest and proper directories.

Frequently Asked Questions about plugin-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scaffold a Claude Code plugin with the correct directory structure?▼

Scaffolding a Claude Code plugin involves generating standardized folders for commands, agents, skills, hooks, and scripts alongside a configured manifest. This ensures proper component placement and sets up auto-discovery for the plugin.

What is the correct directory layout for organizing Claude Code plugin components?▼

The correct directory layout separates components into standardized folders for commands, agents, skills, hooks, and scripts. Using this structure ensures proper component organization and enables reliable auto-discovery by the Claude Code environment.

How do I configure the plugin.json manifest for Claude Code auto-discovery?▼

Configuring the plugin.json manifest requires defining specific fields and following validation rules to enable auto-discovery. Proper manifest management ensures the Claude Code environment can automatically detect and load your plugin components.

Can I audit an existing Claude Code plugin to check its directory structure and manifest?▼

Yes, you can audit existing Claude Code plugins by validating their directory structure and manifest configuration against standardized layout rules. This process checks component placement, path conventions, and auto-discovery setup to ensure consistency.

Do I need external tools to set up a Claude Code plugin directory and manifest?▼

No external tools are required to set up a Claude Code plugin directory and manifest. Scaffolding relies solely on standard file system operations, though optional scripts, references, and assets can be included to enrich functionality.

What's the best way to manage cross-environment paths in a Claude Code plugin?▼

The best way to manage cross-environment paths in a Claude Code plugin is using the `${CLAUDE_PLUGIN_ROOT}` variable. This portable path convention ensures reliable references to commands, hooks, and assets across different environments.