I Built a Complex AI Orchestration System. Then I Deleted 93% of It.

I built Vibe-Claude — a multi-agent orchestration system for Claude Code. Over 4 versions it grew to 13 agents, 8 skills, a 5-phase pipeline, and 8K lines.

Then I deleted almost all of it. Here's why.

The platform was faster than me

Every feature I built, Claude Code shipped natively within weeks:

• My memory system → Auto Memory shipped
• My context compression → Compaction API shipped
• My session restore → built-in
• My orchestrator agent → built-in subagents
• My parallel execution → built-in
• My 13 persona agents → Claude already does all of it

The real problem

My 13 agents were markdown files like "you are an analyst." But Claude doesn't need a costume to analyze code. It already knows how.

Worse — all those prompts consumed context window. Context is the model's working memory. I was filling it with instructions about how to think, leaving less room for actual thinking.

After deleting 93%, Claude performed better on the same tasks.

What survived

Two actual failure modes in practice:

1. Claims "done" without running the code
2. Breaks syntax after edits

v5: 5 rules + 2 hooks. 138 lines. Done.

Lessons

1. The platform will eat your features. What's a plugin today is a built-in tomorrow.
2. Prompts are suggestions, code is enforcement. If you need a guarantee, write a hook, not a markdown file.
3. Less prompting = more capability. Context is finite. Don't waste it on instructions the model already follows.
4. The hardest skill is deletion.

Full postmortem in the README: github.com/kks0488/vibe-claude