Ultra Clean

Turn broad cleanup requests into a disciplined audit plus implementation pass. Default to evidence first, deletion second, abstraction third.

Core Rules

Treat cleanup as behavior-preserving refactor work unless the user explicitly asks for product changes.
Build repo context before editing anything: structure, languages, package manager, validation commands, generated code, framework entry points, and public interfaces.
Run eight cleanup lanes. If the platform caps concurrent subagents, run them in waves, but keep the lane boundaries intact.
Require every lane to produce: a critical assessment, concrete evidence, a recommendation set, implemented high-confidence fixes, and a validation note.
Implement only high-confidence changes. Log medium-confidence ideas without changing code.
Prefer removal over abstraction, and prefer simplification over cleverness.
Never trust one signal alone for deletion or consolidation. Cross-check tool output with code search, runtime entry points, tests, and public API surfaces.
Do not revert unrelated user changes. Work with the current tree as found.