Summary
EveryInc dropped compound-engineering-plugin (18.3K★, trending #1) — an open-source plugin for Claude Code, Codex, Cursor, and more. The philosophy: "Each unit of engineering work should make subsequent units easier — not harder." Instead of accumulating tech debt, it compounds knowledge. 80% planning and review, 20% execution. The result: every code change makes your codebase cleaner, not messier.
The Problem
Traditional software development accumulates technical debt:
- Every feature adds complexity
- Every bug fix leaves behind local knowledge
- Codebase gets larger, context harder to hold
- Each change becomes slower than the last
This is why older codebases are slower to work in than new ones. The default is decay.
The Solution: Compound Engineering
The plugin inverts the default:
Traditional: 20% planning → 80% coding → accumulating debt
Compound: 80% planning → 20% coding → compounding knowledge
It adds these commands to your AI coding tool:
| Command | Purpose |
|---|---|
/ce-brainstorm |
Explore approaches before coding |
/ce-plan |
Detailed implementation plan |
/ce-code-review |
Catch issues early |
/ce-doc-review |
Documentation quality check |
/ce-compound |
Codify knowledge for reuse |
Quick Start
git clone https://github.com/EveryInc/compound-engineering-plugin
cd compound-engineering-plugin
# For Claude Code
cp -r skills/* ~/.claude/skills/
# For Codex CLI
cp skills/* ~/.codex/skills/
Then in your AI coding tool: /ce-plan "Add user authentication"
Why This Matters
The plugin implements a meta-lesson: AI coding tools are only as good as your process. Better prompts help. Better context helps. But better engineering discipline helps most.
The compound effect:
- After 10 changes: Codebase is cleaner than when you started
- After 100 changes: Knowledge is systematized
- After 1,000 changes: Your AI knows your codebase intimately
FAQ
Q: Does this work with any AI coding tool?
A: Yes. Claude Code, Codex CLI, Cursor, Continue.dev, and any tool that supports custom skills.
Q: Is this just a prompt library?
A: No. It's a methodology codified into commands.
Q: How is this different from regular code review?
A: It's proactive, not reactive. You plan AND review before writing.
18.3K★ in days. From EveryInc (Anthropic-backed). The compound effect is real.
Top comments (0)