npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@every-env/compound-plugin

v2.42.0

Published

[![Build Status](https://github.com/EveryInc/compound-engineering-plugin/actions/workflows/ci.yml/badge.svg)](https://github.com/EveryInc/compound-engineering-plugin/actions/workflows/ci.yml) [![npm](https://img.shields.io/npm/v/@every-env/compound-plugin

Readme

Compound Marketplace

Build Status npm

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.

# convert the compound-engineering plugin into OpenCode format
bunx @every-env/compound-plugin install compound-engineering --to opencode

# convert to Codex format
bunx @every-env/compound-plugin install compound-engineering --to codex

# convert to Factory Droid format
bunx @every-env/compound-plugin install compound-engineering --to droid

# convert to Pi format
bunx @every-env/compound-plugin install compound-engineering --to pi

# convert to Gemini CLI format
bunx @every-env/compound-plugin install compound-engineering --to gemini

# convert to GitHub Copilot format
bunx @every-env/compound-plugin install compound-engineering --to copilot

# convert to Kiro CLI format
bunx @every-env/compound-plugin install compound-engineering --to kiro

# convert to OpenClaw format
bunx @every-env/compound-plugin install compound-engineering --to openclaw

# convert to Windsurf format (global scope by default)
bunx @every-env/compound-plugin install compound-engineering --to windsurf

# convert to Windsurf workspace scope
bunx @every-env/compound-plugin install compound-engineering --to windsurf --scope workspace

# convert to Qwen Code format
bunx @every-env/compound-plugin install compound-engineering --to qwen

# auto-detect installed tools and install to all
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:

# add to ~/.zshrc or ~/.bashrc
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

| Target | Output path | Notes | |--------|------------|-------| | 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 (BashExecute, WriteCreate); 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:plancommands/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:

# Sync to all detected tools (default)
bunx @every-env/compound-plugin sync

# Sync skills and MCP servers to OpenCode
bunx @every-env/compound-plugin sync --target opencode

# Sync to Codex
bunx @every-env/compound-plugin sync --target codex

# Sync to Pi
bunx @every-env/compound-plugin sync --target pi

# Sync to Droid
bunx @every-env/compound-plugin sync --target droid

# Sync to GitHub Copilot (skills + MCP servers)
bunx @every-env/compound-plugin sync --target copilot

# Sync to Gemini (skills + MCP servers)
bunx @every-env/compound-plugin sync --target gemini

# Sync to Windsurf
bunx @every-env/compound-plugin sync --target windsurf

# Sync to Kiro
bunx @every-env/compound-plugin sync --target kiro

# Sync to Qwen
bunx @every-env/compound-plugin sync --target qwen

# Sync to OpenClaw (skills only; MCP is validation-gated)
bunx @every-env/compound-plugin sync --target openclaw

# Sync to all detected tools
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)

| Command | Purpose | |---------|---------| | /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