Reducing Entropy

A manual-only skill that optimizes for the smallest possible codebase, not the smallest change. It flips the usual question from "what's the minimal diff" to "what's the minimal result." Measures success by total lines after, not effort expended. Comes with reference mindsets you're required to load before starting. The core heuristic is ruthlessly simple: if a change adds net code to the codebase, reject it, even if it improves organization or flexibility. Best for projects drowning in accumulated complexity where you need philosophical backup to justify aggressive deletion. The red flags section alone is worth reading.