softaworks/agent-toolkit / skills/reducing-entropy
reducing-entropy
VerifiedManual-only skill for minimizing total codebase size. Only activate when explicitly requested by user. Measures success by final code amount, not effort. Bias toward deletion.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 4.7 KB |
| SKILL.md | skill md | 2.5 KB |
| adding-reference-mindsets.md | markdown | 3.3 KB |
| references/data-over-abstractions.md | markdown | 1.8 KB |
| references/design-is-taking-apart.md | markdown | 2.2 KB |
| references/expensive-to-add-later.md | markdown | 2.4 KB |
| references/simplicity-vs-easy.md | markdown | 1.7 KB |
references/design-is-taking-apart.md
View on GitHub---
description: Design is taking things apart, not adding features. Separate concerns, remove dependencies, compose simple pieces.
---
# Composition Over Construction
## The Core Insight
> "Design is about taking things apart."
Good design is not about adding features. It's about removing dependencies. It's about separating concerns so cleanly that each piece can be understood, tested, and changed independently.
## Taking Things Apart
When you see a complex system, the instinct is to understand how the pieces fit together. But the real skill is seeing how to *pull them apart*.
- What different concerns are mixed here?
- Which responsibilities could be separate?
- Where are we conflating different concepts?
Each separation reduces complexity. Each coupling increases it.
## Building from Simple Parts
Once you have simple, independent pieces:
- They compose freely
- They test trivially
- They change safely
Inheritance complects. Composition liberates.
A system built from small, focused functions that transform data is:
- Easier to understand (each piece does one thing)
- Easier to test (pure functions, clear inputs/outputs)
- Easier to change (modify one piece without touching others)
## The Anti-Pattern
The opposite of composition is the "god object" or "kitchen sink" - one thing that knows about everything, does everything, and can't be changed without breaking everything else.
Every helper method you add to a class is a small step toward the kitchen sink. Every layer of abstraction is a coupling waiting to cause pain.
## Practical Application
Before adding a method, wrapper, or abstraction:
- Does this *separate* concerns, or *combine* them?
- Am I making pieces more independent, or more coupled?
- Could I solve this with a function that takes data and returns data?
**Separate, don't combine. Compose, don't construct.**
## External References
- [Simple Made Easy](https://www.infoq.com/presentations/Simple-Made-Easy/) - Rich Hickey on complecting vs composing
- [Out of the Tar Pit](https://curtclifton.net/papers/MosesleyMarks06a.pdf) - Moseley & Marks on essential vs accidental complexity
- [A Philosophy of Software Design](https://www.amazon.com/dp/173210221X) - John Ousterhout on deep vs shallow modules
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |