simplification-cascades_skill

Overview

This skill finds a single insight that removes multiple components and simplifies system design. It trains you to spot unifying principles where many special cases can be collapsed into a single abstraction. The goal is measurable simplification: fewer components, less config, and lower maintenance cost.

How this skill works

The skill inspects a codebase or system for repeated implementations, special‑case handling, and growing configuration surfaces. It guides you to list variations, identify the underlying commonality, and extract a domain‑independent abstraction. You validate the abstraction by testing fit across cases and measuring how many components become unnecessary.

When to use it

• You see the same feature implemented in multiple ways across the system
• Configuration files keep growing with options for edge cases
• Refactoring feels like whack‑a‑mole—fixing one bug creates another
• Many guardrails, locks, or validators that look similar
• You need a high‑impact refactor with measurable ROI

Best practices

• Start by inventorying variations before proposing abstractions
• Prefer simple, well‑documented abstractions over clever designs
• Prototype the abstraction and run it against real cases to validate coverage
• Measure impact: count eliminated implementations, reduced LOC, and simplified configs
• Keep the abstraction orthogonal and domain‑independent where possible

Example use cases

• Replace separate batch/stream/file handlers with a single stream processor plus source adapters
• Unify session tracking, rate limiting, and connection pools under a per‑entity ResourceGovernor
• Adopt immutable data and transformation pipelines to remove locking, defensive copies, and complex cache invalidation
• Convert many special‑case config flags into sane defaults plus a small extension API
• Abstract repeated parsing/validation logic into a single rule engine that covers multiple formats