Dev AI-Slop Cleaner

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Cleanup pass for code generated by AI. Removes the typical bloat: single-use helpers, over-abstractions, generic names like processData(), unnecessary configurability that wasn't asked for.

Use When

• After dev-autopilot finishes a feature
• After @bolt-executor produces a multi-file change
• Post-burst generation that wasn't carefully scoped
• User says "deslop", "clean up the AI slop", "remove the bloat"

Do Not Use When

• Hand-written code (no slop signature)
• Code that's intentionally extensible (talk to @apex-architect first)

What to Look For

Signature 1: Single-use helpers

// SLOP
function calculateSum(a: number, b: number): number { return a + b; }
const total = calculateSum(price, tax);

// CLEANED
const total = price + tax;

Signature 2: Over-abstractions

// SLOP
class TimeoutConfigManager {
  private static instance: TimeoutConfigManager;
  static getInstance() { ... }
  setTimeout(ms: number) { ... }
  getTimeout() { ... }
}

// CLEANED
const TIMEOUT_MS = 5000;

Signature 3: Generic naming

// SLOP
function processData(data: any): any { ... }

// CLEANED
function parseCSVRow(row: string): User { ... }

Signature 4: Unrequested configurability

// SLOP
function fetchUser(id: string, options?: { retries?: number, backoff?: number, timeout?: number, cache?: boolean }) { ... }

// CLEANED (if retries/etc. weren't asked for)
function fetchUser(id: string) { ... }

Signature 5: TODO/HACK comments without context

Remove or convert to actual issues.

Workflow

1. Scan the recent diff for the 5 signatures above
2. For each match, propose the cleaned version
3. Hand off to @bolt-executor to apply (or @zen-simplifier for batch cleanup)
4. Run dev-verify to confirm behavior is unchanged
5. Save report to workspace/development/research/[C]slop-cleanup-{component}-{date}.md

Pairs With

• @zen-simplifier (the agent that does the actual cleanup)
• @bolt-executor (when fixes are simple)
• dev-verify (to confirm zero behavior change)

Anti-patterns

• Removing abstractions that earn their keep (used in 3+ places, complex logic)
• Removing comments that explain non-obvious decisions
• "Improving" code that wasn't slop in the first place