01
What this skill does
Use this skill when a codebase needs aggressive but disciplined simplification. It builds a behavior-preservation oracle, audits removable code, tests deletion and simplification candidates, and pauses for explicit approval before architecture-level refactors so code slimming improves developer experience instead of creating dense or risky code.
02
When to use it
- SignalFinding removable files, branches, exports, dependencies, wrappers, and duplicate logic.
- SignalRunning code-reduction candidates against build, typecheck, test, lint, smoke, or contract oracles.
- SignalDiagnosing architecture problems that block safe deletion and proposing DX-oriented options before refactoring.
03
How it works
- 01
Record baseline files, LOC, bytes, dependencies, large files, duplicate blocks, and generated or vendor directories.
- 02
Run the audit and architecture DX scans when a repository is available.
- 03
Design the strongest available behavior-preservation oracle before deleting code.
- 04
Enumerate deletion, simplification, dependency, config, test, and architecture candidates across every layer.
- 05
Search exact or partitioned candidate sets until no untested candidate remains in the current frontier.
04
What you get back
- SignalBefore and after metrics, accepted candidates, rejected high-risk candidates, and shrink ratio.
- SignalOracle commands and residual blind spots for the final code-reduction result.
- SignalApproval-gated architecture options when structural cleanup is needed before safe slimming.
05
Important boundaries
- SignalDo not count minification, obfuscation, whitespace-only deletion, or comment deletion as code slimming.
- SignalDo not delete public APIs, migrations, compatibility shims, security checks, operational logging, or config without evidence.
- SignalDo not perform architecture-level refactors until the user explicitly approves one option or scope.
06