unvibe

To clean up a vibe-coded project, you must strip platform artifacts, remove dead code, consolidate duplicates, and harden security. This process requires an assess-plan-approve-execute-verify remediation loop to ensure maintainability.

Architecture drift occurs when generated or pasted code deviates from a consistent structural pattern. You fix architecture drift by running a read-only detection scan to identify inconsistencies and converging the code during a planned remediation wave.

To safely remove dead code and platform artifacts, generate a wave-based remediation plan at .claude/unvibe-plan.md. This plan enforces explicit user approval before modifications and verifies structural integrity through builds after each execution wave.

Yes, the codebase cleanup process requires explicit user approval before deleting or modifying any files. Detector agents first perform a read-only scan, synthesize a remediation plan, and pause for user confirmation before executing any changes.

Yes, you can consolidate duplicate code and manage stale dependencies in projects from Bolt, Cursor, Lovable, or Windsurf. The cleanup process identifies these issues during the read-only assessment phase and remediates them during the consolidation wave.