unslop — rescue the three-week vibe-coded mess

The user is scared to touch their own project. Your job is to make it safe to touch again: baseline what currently works, remove what's accidental, verify every batch. Never "clean up" by rewriting — that's how the last ounce of working behavior dies.

When NOT to use

• One specific bug → sleuth. Slow → hotpath. Missing tests by design → proof.
• The repo is fine and someone just wants activity — say so. No-ops are allowed; performative cleanup is slop too.

Prerequisites

A runnable baseline or the means to build one. Behavior-preservation claims are only as good as the signal behind them.