plugin-structure

Organize Claude Code plugin directory structures and manifest configurations.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aah-stack/anthropic --skill plugin-structure-aah-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/aah-stack/anthropic/tree/main/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/aah-stack/anthropic --skill plugin-structure-aah-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers understand and build well-structured Claude Code plugins by providing guidance for organizing components, configuring manifests, and following plugin architecture conventions.

Core Features & Use Cases

  • Plugin Architecture Guidance: Explains directory layouts, component discovery, manifest configuration, and portable path usage for Claude Code plugins.
  • Component Organization: Provides patterns for structuring commands, agents, skills, hooks, scripts, and MCP integrations.
  • Use Case: A developer creating a new Claude Code plugin can use this Skill to scaffold a production-ready structure, configure plugin.json correctly, and organize reusable components.

Quick Start

Use the plugin-structure skill to help me create a Claude Code plugin layout with the correct manifest and component organization.

Frequently Asked Questions about plugin-structure

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

FAQPage Schema
How do I structure a Claude Code plugin with commands, agents, and hooks?

To structure a Claude Code plugin, organize commands, agents, and hooks into a proper directory layout while configuring the plugin.json manifest to ensure correct component discovery and portable resource references.

What is the correct directory layout for a Claude Code plugin?

The correct directory layout for a Claude Code plugin separates commands, agents, skills, hooks, and scripts into organized folders, using portable path references and a central plugin.json manifest for scalable component discovery.

How do I configure plugin.json for a Claude Code extension?

You configure plugin.json for a Claude Code extension by defining the manifest parameters that satisfy naming conventions, enable automatic component discovery, and map portable paths to your integrated MCP resources and hooks.

Does this plugin architecture guidance support MCP integrations?

Yes, this plugin architecture guidance supports MCP integrations by providing specific configuration patterns and directory structures to seamlessly include Model Context Protocol servers within your Claude Code plugin components.

What's the best way to scale a Claude Code plugin with multiple skills and agents?

The best way to scale a Claude Code plugin is to apply modular directory structures and strict naming conventions, ensuring that growing numbers of skills, agents, and hooks remain maintainable and discoverable.

Why use portable path references in Claude Code plugin development?

You use portable path references in Claude Code plugin development to ensure that manifest configurations and component resource links remain valid across different deployment environments and user installations.