Plugin Structure

Name: Plugin Structure
Availability: InStock
Author: RepairYourTech

Guide Claude Code plugin creation with directory structures and manifest configurations.

6|1|Updated Feb 27, 2026

Search Tags:#architecture #scaffolding #claude code #plugin development #manifest #component organization

Ready to run

npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill plugin-structure-repairyourtech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skill-library/meta/claude-code/plugin-structure
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill plugin-structure-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to structuring, configuring, and organizing components for Claude Code plugins, ensuring maintainability and discoverability.

Core Features & Use Cases

Directory Layout: Understand the conventional structure for commands, agents, skills, hooks, and MCP servers.
Manifest Configuration: Learn to define plugin metadata and component paths in plugin.json.
Component Organization: Best practices for naming and structuring individual components.
Portable Paths: Master the use of ${CLAUDE_PLUGIN_ROOT} for cross-platform compatibility.
Use Case: You're starting a new Claude Code plugin and need to know where to place your command files, how to define your plugin's name and version, and how to reference helper scripts reliably.

Quick Start

Refer to the Plugin Structure skill to understand the standard directory layout for a Claude Code plugin.

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 for commands, agents, and hooks?▼

Structure a Claude Code plugin by organizing commands, agents, skills, hooks, and MCP servers into conventional directories. Adhere to specific file naming conventions to ensure components are maintainable and support auto-discovery within the plugin architecture.

What is the best way to configure plugin metadata in a manifest?▼

The best way to configure plugin metadata is by defining component paths and plugin properties like name and version in the `plugin.json` manifest. This configuration ensures proper component organization and system discoverability.

How do I use portable paths for helper scripts in plugin development?▼

Use portable paths for helper scripts by referencing the `${CLAUDE_PLUGIN_ROOT}` variable for path resolution. This ensures cross-platform compatibility and reliable script execution across different environments during plugin development.

Where should I place command files when scaffolding a new plugin?▼

Place command files in the standard directory layout designated for commands when scaffolding a new plugin. Following this conventional directory structure ensures your commands are correctly auto-discovered by the system.

Does plugin architecture require specific naming conventions for MCP servers?▼

Yes, plugin architecture requires adherence to specific file naming conventions for MCP servers and other components. Following these naming best practices ensures proper auto-discovery and maintainable component organization.