Negentropy Lens

bencium/bencium-claude-code-design-skill

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.

skills.sh installs: 291
GitHub stars: 267
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-claude-code-design-skill --skill negentropy-lens --agent claude-code

Installs into .claude/skills of the current project.

Files

Negentropy Lens

A thinking framework for evaluating decisions, systems, and architectures through two fundamental system states: entropy (decay, disorder, complexity debt) and negentropy (growth, compounding value, increasing order).

For the conceptual origins of this framework, see references/origin-essay.md.

Core Principle

Every system exists in one of two states. Every decision either accelerates entropy or drives negentropy. There is no neutral. Inaction is entropic. The goal is not to eliminate entropy — it is to recognize which state a system is in, surface what is hidden, and make deliberate choices about direction.

Term Definitions

On first use in every output, define these three terms inline using parentheses:

Entropy (the natural tendency of systems toward decay, disorder, and complexity without value)
Negentropy (the deliberate reversal of decay — growth, compounding value, increasing order)
Tacit knowledge (the unwritten, unspoken knowledge of how things actually work — assumptions, workarounds, and institutional memory that never make it into documentation)

SKILL.md on GitHub