mirror of
https://github.com/anthropics/claude-plugins-official.git
synced 2026-02-05 21:43:08 +00:00
Skills and commands are now merged, so SKILL.md name fields surface in the UI as slash commands. Upper Space names like 'Hook Development' become '/Hook Development', which doesn't work since user-invoked commands don't support spaces. Rename all affected SKILL.md name fields to lower-kebab-case: - hookify: Writing Hookify Rules -> writing-hookify-rules - plugin-dev: Agent Development -> agent-development - plugin-dev: Command Development -> command-development - plugin-dev: Hook Development -> hook-development - plugin-dev: MCP Integration -> mcp-integration - plugin-dev: Plugin Settings -> plugin-settings - plugin-dev: Plugin Structure -> plugin-structure - plugin-dev: Skill Development -> skill-development Also update references in plugin-dev/README.md.
Plugin Structure Skill
Comprehensive guidance on Claude Code plugin architecture, directory layout, and best practices.
Overview
This skill provides detailed knowledge about:
- Plugin directory structure and organization
plugin.jsonmanifest configuration- Component organization (commands, agents, skills, hooks)
- Auto-discovery mechanisms
- Portable path references with
${CLAUDE_PLUGIN_ROOT} - File naming conventions
Skill Structure
SKILL.md (1,619 words)
Core skill content covering:
- Directory structure overview
- Plugin manifest (plugin.json) fields
- Component organization patterns
- ${CLAUDE_PLUGIN_ROOT} usage
- File naming conventions
- Auto-discovery mechanism
- Best practices
- Common patterns
- Troubleshooting
References
Detailed documentation for deep dives:
-
manifest-reference.md: Complete
plugin.jsonfield reference- All field descriptions and examples
- Path resolution rules
- Validation guidelines
- Minimal vs. complete manifest examples
-
component-patterns.md: Advanced organization patterns
- Component lifecycle (discovery, activation)
- Command organization patterns
- Agent organization patterns
- Skill organization patterns
- Hook organization patterns
- Script organization patterns
- Cross-component patterns
- Best practices for scalability
Examples
Three complete plugin examples:
-
minimal-plugin.md: Simplest possible plugin
- Single command
- Minimal manifest
- When to use this pattern
-
standard-plugin.md: Well-structured production plugin
- Multiple components (commands, agents, skills, hooks)
- Complete manifest with metadata
- Rich skill structure
- Integration between components
-
advanced-plugin.md: Enterprise-grade plugin
- Multi-level organization
- MCP server integration
- Shared libraries
- Configuration management
- Security automation
- Monitoring integration
When This Skill Triggers
Claude Code activates this skill when users:
- Ask to "create a plugin" or "scaffold a plugin"
- Need to "understand plugin structure"
- Want to "organize plugin components"
- Need to "set up plugin.json"
- Ask about "${CLAUDE_PLUGIN_ROOT}" usage
- Want to "add commands/agents/skills/hooks"
- Need "configure auto-discovery" help
- Ask about plugin architecture or best practices
Progressive Disclosure
The skill uses progressive disclosure to manage context:
- SKILL.md (~1600 words): Core concepts and workflows
- References (~6000 words): Detailed field references and patterns
- Examples (~8000 words): Complete working examples
Claude loads references and examples only as needed based on the task.
Related Skills
This skill works well with:
- hook-development: For creating plugin hooks
- mcp-integration: For integrating MCP servers (when available)
- marketplace-publishing: For publishing plugins (when available)
Maintenance
To update this skill:
- Keep SKILL.md lean and focused on core concepts
- Move detailed information to references/
- Add new examples/ for common patterns
- Update version in SKILL.md frontmatter
- Ensure all documentation uses imperative/infinitive form