reducing-entropy

Guides code refactoring decisions toward minimizing total codebase size through deletion-biased evaluation.

Updated May 16, 2026
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill reducing-entropy-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reducing-entropy
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/reducing-entropy
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill reducing-entropy-michalo1334

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebases naturally grow over time, accumulating complexity, maintenance burden, and bugs. This Skill counters that trend by evaluating every change based on whether it reduces the total amount of code in the final result, rather than minimizing immediate effort. ## Core Features & Use Cases - Deletion-Biased Evaluation: Applies three core questions to every change—what is the smallest codebase that solves this, does the result reduce total code, and what can be deleted. - Reference Mindsets: Loads philosophical frameworks from the references directory (such as simplicity-vs-easy, data-over-abstractions, and PAGNI) to ground simplification decisions before starting work. - Anti-Pattern Detection: Rejects common excuses for adding code, including status quo bias, speculative flexibility, and unnecessary abstraction layers. - Use Case: When asked to add validation to five forms, instead of creating six new files, the Skill guides you to consolidate forms and logic, potentially reducing the codebase by 150 lines while preserving functionality. ## Quick Start Ask the AI to reduce entropy in a specific module by applying the reducing-entropy skill and loading a reference mindset before proposing deletions.

Frequently Asked Questions about reducing-entropy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce codebase size during refactoring?▼

Evaluate each change by counting lines, files, and functions before and after. Accept only changes where the final total is smaller, and actively look for code made obsolete by the change that can also be deleted.

What is the reducing-entropy skill used for?▼

It is a manual-only skill for minimizing total codebase size, activated only when explicitly requested. It biases toward deletion and aggressive simplification, measuring success by final code amount rather than effort spent.

When should I not apply aggressive code deletion?▼

Avoid it when the codebase is already minimal for its purpose, when working in frameworks with strong conventions, or when regulatory and compliance requirements mandate specific structures. Also skip it when the user accepts the code cost of new functionality.

What is the difference between YAGNI and PAGNI?▼

YAGNI says do not build features until needed, but PAGNI identifies exceptions where retrofitting is dramatically more expensive, such as timestamps, audit logs, API versioning, and logging infrastructure. PAGNI applies only when retrofit costs exceed 10x and the addition is cheap now.

Why does the skill require loading a reference mindset first?▼

Reference mindsets provide philosophical grounding for radical simplification beyond mechanical checklists. Loading at least one, such as simplicity-vs-easy or design-is-taking-apart, calibrates decisions before evaluating what to delete.