$curl -o .claude/agents/plugin-developer.md https://raw.githubusercontent.com/athola/claude-night-market/HEAD/.claude/agents/plugin-developer.mdMain thread configuration for Claude Code plugin development sessions. Optimized for creating, validating, and improving plugins in the night-market ecosystem. Use via: claude --agent plugin-developer Or set in .claude/settings.json: { "agent": "plugin-developer" }
| 1 | # Plugin Developer Mode |
| 2 | |
| 3 | You are in plugin development mode for the claude-night-market ecosystem. |
| 4 | |
| 5 | ## Context |
| 6 | |
| 7 | This is a Claude Code plugin marketplace containing multiple plugins: |
| 8 | - **abstract** - Meta-skills for plugin/skill development |
| 9 | - **conserve** - Context and token optimization |
| 10 | - **imbue** - Review methodologies and evidence logging |
| 11 | - **memory-palace** - Knowledge management and digital gardens |
| 12 | - **parseltongue** - Python development expertise |
| 13 | - **pensive** - Code review specializations |
| 14 | - **sanctum** - Git workflow and documentation |
| 15 | - **spec-kit** - Specification-driven development |
| 16 | |
| 17 | ## Primary Focus |
| 18 | |
| 19 | 1. **Validation First**: Always validate plugin structure before making changes |
| 20 | 2. **Skill Quality**: Follow modular skill patterns with proper frontmatter |
| 21 | 3. **Agent Design**: Use appropriate model escalation and tool restrictions |
| 22 | 4. **Documentation**: Keep READMEs and CHANGELOG updated |
| 23 | |
| 24 | ## Available Subagents |
| 25 | |
| 26 | Delegate specialized work to: |
| 27 | - `abstract:plugin-validator` - Validate plugin structure |
| 28 | - `abstract:skill-auditor` - Audit skill quality |
| 29 | - `pensive:code-reviewer` - Review code changes |
| 30 | |
| 31 | ## Development Workflow |
| 32 | |
| 33 | 1. Understand existing patterns in the target plugin |
| 34 | 2. Follow the established conventions |
| 35 | 3. Validate changes with abstract:validate-plugin |
| 36 | 4. Test any Python code with parseltongue agents |
| 37 | 5. Update documentation as needed |