plugin-structure

Organize Claude Code plugin directories, manifests, and components for auto-discovery.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill plugin-structure-softee-p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/softee-p/redwoodSDK-toolkit/tree/main/dev-plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill plugin-structure-softee-p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Plugin Structure skill provides a clear, reusable blueprint for building Claude Code plugins by outlining directories, manifests, and component organization to ensure consistent discovery and integration.

Core Features & Use Cases

  • Defines standard directory layouts (commands, agents, skills, hooks) and the required placement of plugin.json under .claude-plugin
  • Demonstrates how to structure SKILL.md for auto-discovery, including optional supporting folders like scripts/, references/, and assets/
  • Guides users on maintenance and best practices for scalable plugin architectures across small prototypes and production-grade extensions

Quick Start

Create a minimal plugin skeleton with a plugin.json and a single SKILL.md to enable auto-discovery.

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 auto-discovery?

To structure a Claude Code plugin for auto-discovery, place a plugin.json manifest under the .claude-plugin directory and organize components into standard folders like commands, agents, skills, and hooks.

What is the SKILL.md convention and how does it work in plugin development?

The SKILL.md convention defines how a plugin skill is documented and located. Placing a SKILL.md file in your plugin directory enables Claude Code to automatically discover and integrate the skill during runtime.

What directory layout should I use when scaffolding a plugin skeleton?

A standard plugin directory layout separates components into commands, agents, skills, and hooks folders, while optional supporting directories like scripts, references, and assets hold auxiliary files for scalable architecture.

Can I use this plugin structure guidance for production-grade extensions?

Yes, the plugin structure guidance applies to both small prototypes and production-grade extensions, providing best practices for scalable organization, reliable discovery, and ongoing maintenance of plugin architectures.

Why does my Claude Code plugin not get discovered automatically?

Auto-discovery fails when the plugin.json manifest is missing from the .claude-plugin directory or the SKILL.md file does not follow the required conventions for component organization and directory placement.