intuitive-reduce-entropylisted

# Intuitive Reduce Entropy Use this skill as the maintenance entrypoint when the user does not already know which repo surface most needs cleanup. It diagnoses likely entropy sources, recommends one bounded slice, and routes to the specialist skill that owns that slice. The default goal is a repo where future agents can start quickly, humans can review current truth from a small doc surface, tests show real behavior, and the next meaningful task does not require rediscovering stale paths, bloated agent files, mixed doc tiers, or unclear cleanup targets. ## Zen Of Python Bias Rank cleanup candidates with an explicit Zen of Python-style bias. Prefer maintenance slices that make the repo more obvious, readable, flat, explicit, and unsurprising for the next human or agent. - Prefer explicit current truth over implicit tribal knowledge. - Prefer one obvious canonical path, command, API, or doc home over parallel near-equivalents. - Prefer simple, direct structure over clever indirection, deep nesting, or special-case wrappers. - Make exceptional compatibility, migration, or verification constraints explicit instead of hiding them behind silent fallbacks. - Let practicality beat purity, but choose the practical slice that most reduces future rediscovery and surprise. - If the best slice is not obvious after inspection, say so and show the tradeoff instead of forcing artificial certainty. When presenting candidates, include a brief `Zen hint:` for the recommended sli