Compound Marketplace

A Claude Code plugin marketplace featuring the Compound Engineering Plugin — tools that make each unit of engineering work easier than the last.
Claude Code Install
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering
Cursor Install
/add-plugin compound-engineering
OpenCode, Codex, Droid, Pi, Gemini, Copilot, Kiro, Windsurf, OpenClaw & Qwen (experimental) Install
This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Pi, Gemini CLI, GitHub Copilot, Kiro CLI, Windsurf, OpenClaw, and Qwen Code.
bunx @every-env/compound-plugin install compound-engineering --to opencode
bunx @every-env/compound-plugin install compound-engineering --to codex
bunx @every-env/compound-plugin install compound-engineering --to droid
bunx @every-env/compound-plugin install compound-engineering --to pi
bunx @every-env/compound-plugin install compound-engineering --to gemini
bunx @every-env/compound-plugin install compound-engineering --to copilot
bunx @every-env/compound-plugin install compound-engineering --to kiro
bunx @every-env/compound-plugin install compound-engineering --to openclaw
bunx @every-env/compound-plugin install compound-engineering --to windsurf
bunx @every-env/compound-plugin install compound-engineering --to windsurf --scope workspace
bunx @every-env/compound-plugin install compound-engineering --to qwen
bunx @every-env/compound-plugin install compound-engineering --to all
Local Development
When developing and testing local changes to the plugin:
Claude Code — add a shell alias so your local copy loads alongside your normal plugins:
alias claude-dev-ce='claude --plugin-dir ~/code/compound-engineering-plugin/plugins/compound-engineering'
One-liner to append it:
echo "alias claude-dev-ce='claude --plugin-dir ~/code/compound-engineering-plugin/plugins/compound-engineering'" >> ~/.zshrc
Then run claude-dev-ce instead of claude to test your changes. Your production install stays untouched.
Codex — point the install command at your local path:
bun run src/index.ts install ./plugins/compound-engineering --to codex
Other targets — same pattern, swap the target:
bun run src/index.ts install ./plugins/compound-engineering --to opencode
Output format details per target
opencode | ~/.config/opencode/ | Commands as .md files; opencode.json MCP config deep-merged; backups made before overwriting |
codex | ~/.codex/prompts + ~/.codex/skills | Claude commands become prompt + skill pairs; canonical ce:* workflow skills also get prompt wrappers; deprecated workflows:* aliases are omitted |
droid | ~/.factory/ | Tool names mapped (Bash→Execute, Write→Create); namespace prefixes stripped |
pi | ~/.pi/agent/ | Prompts, skills, extensions, and mcporter.json for MCPorter interoperability |
gemini | .gemini/ | Skills from agents; commands as .toml; namespaced commands become directories (workflows:plan → commands/workflows/plan.toml) |
copilot | .github/ | Agents as .agent.md with Copilot frontmatter; MCP env vars prefixed with COPILOT_MCP_ |
kiro | .kiro/ | Agents as JSON configs + prompt .md files; only stdio MCP servers supported |
openclaw | ~/.openclaw/extensions/<plugin>/ | Entry-point TypeScript skill file; openclaw-extension.json for MCP servers |
windsurf | ~/.codeium/windsurf/ (global) or .windsurf/ (workspace) | Agents become skills; commands become flat workflows; mcp_config.json merged |
qwen | ~/.qwen/extensions/<plugin>/ | Agents as .yaml; env vars with placeholders extracted as settings; colon separator for nested commands |
All provider targets are experimental and may change as the formats evolve.
Sync Personal Config
Sync your personal Claude Code config (~/.claude/) to other AI coding tools. Omit --target to sync to all detected supported tools automatically:
bunx @every-env/compound-plugin sync
bunx @every-env/compound-plugin sync --target opencode
bunx @every-env/compound-plugin sync --target codex
bunx @every-env/compound-plugin sync --target pi
bunx @every-env/compound-plugin sync --target droid
bunx @every-env/compound-plugin sync --target copilot
bunx @every-env/compound-plugin sync --target gemini
bunx @every-env/compound-plugin sync --target windsurf
bunx @every-env/compound-plugin sync --target kiro
bunx @every-env/compound-plugin sync --target qwen
bunx @every-env/compound-plugin sync --target openclaw
bunx @every-env/compound-plugin sync --target all
This syncs:
- Personal skills from
~/.claude/skills/ (as symlinks)
- Personal slash commands from
~/.claude/commands/ (as provider-native prompts, workflows, or converted skills where supported)
- MCP servers from
~/.claude/settings.json
Skills are symlinked (not copied) so changes in Claude Code are reflected immediately.
Supported sync targets:
opencode
codex
pi
droid
copilot
gemini
windsurf
kiro
qwen
openclaw
Notes:
- Codex sync preserves non-managed
config.toml content and now includes remote MCP servers.
- Command sync reuses each provider's existing Claude command conversion, so some targets receive prompts or workflows while others receive converted skills.
- Copilot sync writes personal skills to
~/.copilot/skills/ and MCP config to ~/.copilot/mcp-config.json.
- Gemini sync writes MCP config to
~/.gemini/ and avoids mirroring skills that Gemini already discovers from ~/.agents/skills, which prevents duplicate-skill warnings.
- Droid, Windsurf, Kiro, and Qwen sync merge MCP servers into the provider's documented user config.
- OpenClaw currently syncs skills only. Personal command sync is skipped because this repo does not yet have a documented user-level OpenClaw command surface, and MCP sync is skipped because the current official OpenClaw docs do not clearly document an MCP server config contract.
Workflow
Brainstorm → Plan → Work → Review → Compound → Repeat
↑
Ideate (optional — when you need ideas)
/ce:ideate | Discover high-impact project improvements through divergent ideation and adversarial filtering |
/ce:brainstorm | Explore requirements and approaches before planning |
/ce:plan | Turn feature ideas into detailed implementation plans |
/ce:work | Execute plans with worktrees and task tracking |
/ce:review | Multi-agent code review before merging |
/ce:compound | Document learnings to make future work easier |
The /ce:ideate skill proactively surfaces strong improvement ideas, and /ce:brainstorm then clarifies the selected one before committing to a plan.
Each cycle compounds: brainstorms sharpen plans, plans inform future plans, reviews catch more issues, patterns get documented.
Philosophy
Each unit of engineering work should make subsequent units easier—not harder.
Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.
Compound engineering inverts this. 80% is in planning and review, 20% is in execution:
- Plan thoroughly before writing code
- Review to catch issues and capture learnings
- Codify knowledge so it's reusable
- Keep quality high so future changes are easy
Learn More