mirror of
https://github.com/anthropics/claude-code.git
synced 2025-11-28 16:50:27 +08:00
387dc35db7Adds the plugin-dev plugin to public marketplace. A comprehensive toolkit for
developing Claude Code plugins with 7 expert skills, 3 AI-assisted agents, and
extensive documentation covering the complete plugin development lifecycle.
Key features:
- 7 skills: hook-development, mcp-integration, plugin-structure, plugin-settings,
command-development, agent-development, skill-development
- 3 agents: agent-creator (AI-assisted generation), plugin-validator (structure
validation), skill-reviewer (quality review)
- 1 command: /plugin-dev:create-plugin (guided 8-phase workflow)
- 10 utility scripts for validation and testing
- 21 reference docs with deep-dive guidance (~11k words)
- 9 working examples demonstrating best practices
Changes for public release:
- Replaced all references to internal repositories with "Claude Code"
- Updated MCP examples: internal.company.com → api.example.com
- Updated token variables: ${INTERNAL_TOKEN} → ${API_TOKEN}
- Reframed agent-creation-system-prompt as "proven in production"
- Preserved all ${CLAUDE_PLUGIN_ROOT} references (186 total)
- Preserved valuable test blocks in core modules
Validation:
- All 3 agents validated successfully with validate-agent.sh
- All JSON files validated with jq
- Zero internal references remaining
- 59 files migrated, 21,971 lines added
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
109 lines
3.1 KiB
Markdown
109 lines
3.1 KiB
Markdown
# 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.json` manifest 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.json` field 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:
|
|
|
|
1. **SKILL.md** (~1600 words): Core concepts and workflows
|
|
2. **References** (~6000 words): Detailed field references and patterns
|
|
3. **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:
|
|
1. Keep SKILL.md lean and focused on core concepts
|
|
2. Move detailed information to references/
|
|
3. Add new examples/ for common patterns
|
|
4. Update version in SKILL.md frontmatter
|
|
5. Ensure all documentation uses imperative/infinitive form
|