Features: - 30+ Custom Skills (cognitive, development, UI/UX, autonomous agents) - RalphLoop autonomous agent integration - Multi-AI consultation (Qwen) - Agent management system with sync capabilities - Custom hooks for session management - MCP servers integration - Plugin marketplace setup - Comprehensive installation script Components: - Skills: always-use-superpowers, ralph, brainstorming, ui-ux-pro-max, etc. - Agents: 100+ agents across engineering, marketing, product, etc. - Hooks: session-start-superpowers, qwen-consult, ralph-auto-trigger - Commands: /brainstorm, /write-plan, /execute-plan - MCP Servers: zai-mcp-server, web-search-prime, web-reader, zread - Binaries: ralphloop wrapper Installation: ./supercharge.sh
3.5 KiB
3.5 KiB
Contributing to claude-delegator
Contributions welcome. This document covers how to contribute effectively.
Quick Start
# Clone the repo
git clone https://github.com/jarrodwatts/claude-delegator
cd claude-delegator
# Install plugin in Claude Code
/claude-delegator:setup
# Test your changes by invoking the oracle
What to Contribute
| Area | Examples |
|---|---|
| New Providers | Ollama, Mistral, local model integrations |
| Role Prompts | New roles for prompts/, improved existing prompts |
| Rules | Better delegation triggers, model selection logic |
| Bug Fixes | Command issues, error messages |
| Documentation | README improvements, examples, troubleshooting |
Project Structure
claude-delegator/
├── .claude-plugin/ # Plugin manifest
│ └── plugin.json
├── commands/ # Slash commands (/setup, /uninstall)
├── rules/ # Orchestration logic (installed to ~/.claude/rules/)
├── prompts/ # Role prompts (oracle, momus)
├── config/ # Provider registry
├── CLAUDE.md # Development guidance for Claude Code
└── README.md # User-facing docs
Pull Request Process
Before Submitting
- Test your changes - Run
/claude-delegator:setupand verify - Update docs - If you change behavior, update relevant docs
- Keep commits atomic - One logical change per commit
PR Guidelines
| Do | Don't |
|---|---|
| Focus on one change | Bundle unrelated changes |
| Write clear commit messages | Leave vague descriptions |
| Test with actual MCP calls | Assume it works |
| Update CLAUDE.md if needed | Ignore developer docs |
Commit Message Format
type: short description
Longer explanation if needed.
Types: feat, fix, docs, refactor, chore
Examples:
feat: add Ollama provider supportfix: handle Codex timeout correctlydocs: add troubleshooting for auth issues
Adding a New Provider
-
Check native MCP support - If the CLI has
mcp-serverlike Codex, no wrapper needed -
Create MCP wrapper (if needed):
servers/your-provider-mcp/ ├── src/ │ └── index.ts ├── package.json └── tsconfig.json -
Add to providers.json:
{ "your-provider": { "cli": "your-cli", "mcp": { ... }, "roles": ["oracle"], "strengths": ["what it's good at"] } } -
Add role prompts (optional):
prompts/your-role.md -
Update setup command - Add checks for the new CLI
-
Document in README - Add to provider tables
Code Style
Markdown (Rules/Prompts)
- Use tables for structured data
- Keep prompts concise and actionable
- Test with actual Claude Code usage
TypeScript (if adding MCP servers)
- No
anywithout explicit justification - No
@ts-ignoreor@ts-expect-error - Use explicit return types on exported functions
Testing
Manual Testing
After changes, verify with actual MCP calls:
- Install the plugin in Claude Code
- Run
/claude-delegator:setup - Verify MCP tools are available (
mcp__codex__codex) - Test MCP tool calls via oracle delegation
- Verify responses are properly synthesized
- Test error cases (timeout, missing CLI)
Questions?
Open an issue for:
- Feature requests
- Bug reports
- Documentation gaps
- Architecture discussions