I Built an Enhancement Layer for Claude Code - No Modifications Required

The Problem

Claude Code is powerful. But after using it for months, I
noticed patterns:

• Context window runs out mid-task
• Same errors repeat without learning
• Complex tasks need clarification upfront
• No checkpoint = lost progress when sessions die

I didn't want to replace Claude Code. I wanted to enhance
it.

## The Solution: An Enhancement Layer

Vibe-Claude is a set of markdown files that sit on top of
vanilla Claude Code. No modifications to Claude Code itself.

~/.claude/
├── CLAUDE.md # System prompt enhancements
├── skills/ # Capability modules
│ ├── vibe/ # Core orchestration
│ ├── v-turbo/ # Parallel execution
│ └── ...
└── agents/ # 13 specialized agents

Install:

bash
  git clone https://github.com/kks0488/vibe-claude
  ~/.claude-vibe
  cp -r ~/.claude-vibe/* ~/.claude/

  That's it. No config files. No API keys. No complex setup.

  What It Adds

  1. Multi-Agent Orchestration

  Instead of one Claude doing everything, tasks are delegated to
   specialists:
  ┌────────┬────────────────────────────────┬────────────────┐
  │  Tier  │             Agents             │    Purpose     │
  ├────────┼────────────────────────────────┼────────────────┤
  │ Opus   │ v-analyst, v-planner, v-critic │ Heavy thinking │
  ├────────┼────────────────────────────────┼────────────────┤
  │ Sonnet │ v-worker, v-designer           │ Execution      │
  ├────────┼────────────────────────────────┼────────────────┤
  │ Haiku  │ v-finder, v-writer             │ Speed tasks    │
  └────────┴────────────────────────────────┴────────────────┘
  /vibe build a dashboard with charts

  Claude (Conductor):
  ├─ v-analyst: Analyze requirements
  ├─ v-finder: Find existing patterns
  ├─ v-worker: Build components
  ├─ v-designer: Style the UI
  └─ v-critic: Review quality

  2. Context Management

  Context window is the most valuable resource. Vibe-Claude
  treats it that way.

  100% ████████████████████ Fresh session
   60% ████████████░░░░░░░░ Caution → compress
   40% ████████░░░░░░░░░░░░ WARNING → checkpoint
   20% ████░░░░░░░░░░░░░░░░ DANGER → clear

  Key rules:
  - Subagent-First: Exploration delegated to agents, main
  context protected
  - Two-Strike Rule: Same failure twice → evaluate context →
  compress or clear
  - Checkpoints: Save progress at phase completion

  3. Dynamic Routing

  Not every task needs the full workflow:
  Complexity: TRIVIAL
  Route: Execute only
  Example: "Fix typo in README"
  ────────────────────────────────────────
  Complexity: SIMPLE
  Route: Recon → Execute → Verify
  Example: "Add error handling"
  ────────────────────────────────────────
  Complexity: MODERATE
  Route: Recon → Execute → Verify
  Example: "Build login page"
  ────────────────────────────────────────
  Complexity: COMPLEX
  Route: Interview → Recon → Plan → Execute → Verify → Polish
  Example: "Refactor auth system"
  4. Interview Protocol (for Complex Tasks)

  Before starting complex work, Claude asks clarifying
  questions:

  Claude: Before I start, a few questions:

  SCOPE
  - Should this include OAuth or just email/password?
  - Admin panel included or separate task?

  TECHNICAL
  - Any existing auth patterns I should follow?
  - Session storage preference (JWT, cookies)?

  EDGE CASES
  - Behavior on failed login attempts?
  - Password reset flow needed?

  VERIFICATION
  - What tests should pass when done?

  This prevents the "I built the wrong thing" problem.

  5. Failure Pattern Detection

  Vibe-Claude recognizes common anti-patterns:
  ┌─────────────────┬─────────────────────────┬────────────────┐
  │     Pattern     │       What It Is        │ Auto-Response  │
  ├─────────────────┼─────────────────────────┼────────────────┤
  │ Kitchen Sink    │ Multiple unrelated      │ Split sessions │
  │                 │ tasks                   │                │
  ├─────────────────┼─────────────────────────┼────────────────┤
  │ Death Spiral    │ Fix breaks something,   │ Clear + root   │
  │                 │ fix that breaks another │ cause          │
  ├─────────────────┼─────────────────────────┼────────────────┤
  │ Infinite        │ Reading files without   │ Stop +         │
  │ Exploration     │ clear goal              │ delegate       │
  ├─────────────────┼─────────────────────────┼────────────────┤
  │ Trust-Verify    │ "Should work" without   │ Run actual     │
  │ Gap             │ proof                   │ tests          │
  └─────────────────┴─────────────────────────┴────────────────┘
  6. Evidence-Based Completion

  Nothing is "done" without proof:

  ✓ Code runs: [actual output pasted]
  ✓ Tests pass: 12 passed, 0 failed
  ✓ Features verified:
    - Login: src/auth/login.ts:42
    - Logout: src/auth/logout.ts:18
  ✓ Tribunal approved

  Forbidden phrases:
  - "Should work" → Must test
  - "I think it's done" → Must prove
  - "Looks correct" → Must run

  Usage

  # Simple task
  /vibe add dark mode toggle

  # Complex task (triggers interview)
  /vibe refactor the entire authentication system

  # With specific skills
  /vibe build landing page  # auto-activates v-style
  /vibe fix this bug        # auto-activates v-analyst

  The Philosophy

  "Don't think. Just vibe."

  Traditional development:
  1. Write requirements
  2. Design architecture
  3. Write code
  4. Write tests
  5. Debug
  6. Repeat...

  Vibe coding:
  1. "Make this"
  2. Done

  Is it expensive (Opus usage)? Yes.
  Does it work? Also yes.

  What's New in v2.1.0

  - Context management with budget visualization
  - Interview protocol for complex tasks
  - Anti-pattern detection and recovery
  - Batch operations with parallel workers
  - Enhanced session management with checkpoints

  Try It

  git clone https://github.com/kks0488/vibe-claude
  ~/.claude-vibe
  cp -r ~/.claude-vibe/* ~/.claude/

  Then open Claude Code and try:

  /vibe build me something cool

  GitHub: https://github.com/kks0488/vibe-claude

  ---
  Questions? Feedback? Let me know in the comments.