simplification-cascades
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
When & Why to Use This Skill
The Simplification Cascades Claude skill is a powerful tool for software architects and developers designed to eliminate system complexity. It focuses on identifying 'unifying principles'—singular insights that make multiple redundant components, special cases, or complex configurations unnecessary. By applying this skill, users can achieve 10x improvements in code maintainability and system elegance by collapsing technical debt into streamlined, high-level abstractions.
Use Cases
- Refactoring Redundant Implementations: Identifying commonalities between disparate modules (like batch vs. real-time processors) to create a single, unified stream abstraction.
- Eliminating Edge Case Bloat: Replacing growing lists of 'if-else' special cases with a general-purpose rule that handles all scenarios inherently.
- System Consolidation: Merging multiple custom enforcement systems (like session tracking and rate limiting) into a single, robust resource governance framework.
- Technical Debt Reduction: Using the 'Everything is a special case of...' principle to delete large portions of unnecessary code while maintaining full functionality.
| name | Simplification Cascades |
|---|---|
| description | Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z" |
| when_to_use | when implementing the same concept multiple ways, accumulating special cases, or complexity is spiraling |
| version | 1.1.0 |
Simplification Cascades
Overview
Sometimes one insight eliminates 10 things. Look for the unifying principle that makes multiple components unnecessary.
Core principle: "Everything is a special case of..." collapses complexity dramatically.
Quick Reference
| Symptom | Likely Cascade |
|---|---|
| Same thing implemented 5+ ways | Abstract the common pattern |
| Growing special case list | Find the general case |
| Complex rules with exceptions | Find the rule that has no exceptions |
| Excessive config options | Find defaults that work for 95% |
The Pattern
Look for:
- Multiple implementations of similar concepts
- Special case handling everywhere
- "We need to handle A, B, C, D differently..."
- Complex rules with many exceptions
Ask: "What if they're all the same thing underneath?"
Examples
Cascade 1: Stream Abstraction
Before: Separate handlers for batch/real-time/file/network data Insight: "All inputs are streams - just different sources" After: One stream processor, multiple stream sources Eliminated: 4 separate implementations
Cascade 2: Resource Governance
Before: Session tracking, rate limiting, file validation, connection pooling (all separate) Insight: "All are per-entity resource limits" After: One ResourceGovernor with 4 resource types Eliminated: 4 custom enforcement systems
Cascade 3: Immutability
Before: Defensive copying, locking, cache invalidation, temporal coupling Insight: "Treat everything as immutable data + transformations" After: Functional programming patterns Eliminated: Entire classes of synchronization problems
Process
- List the variations - What's implemented multiple ways?
- Find the essence - What's the same underneath?
- Extract abstraction - What's the domain-independent pattern?
- Test it - Do all cases fit cleanly?
- Measure cascade - How many things become unnecessary?
Red Flags You're Missing a Cascade
- "We just need to add one more case..." (repeating forever)
- "These are all similar but different" (maybe they're the same?)
- Refactoring feels like whack-a-mole (fix one, break another)
- Growing configuration file
- "Don't touch that, it's complicated" (complexity hiding pattern)
Remember
- Simplification cascades = 10x wins, not 10% improvements
- One powerful abstraction > ten clever hacks
- The pattern is usually already there, just needs recognition
- Measure in "how many things can we delete?"