This is a structured thinking framework for evaluating technical decisions by asking whether they're fighting entropy (decay, complexity debt, hidden knowledge) or creating negentropy (compounding value, captured knowledge, upward spirals). It walks you through mapping a system, diagnosing what's actually rotting versus what's compounding, surfacing the tacit knowledge that lives in people's heads, then evaluating your options with those dimensions in mind. Use it for architecture reviews, comparing technical approaches, or auditing systems that feel stable but might be quietly decaying. The framework is opinionated about one thing: there's no neutral state, and the stuff that feels fine because "someone just knows how it works" is usually your biggest risk.
npx skills add https://github.com/bencium/bencium-claude-code-design-skill --skill negentropy-lens