simplify
When a solution (code, architecture, docs etc.) needs to be simplifed, use this skill with orchestrate-map-reduce to find its essence.
When & Why to Use This Skill
The 'simplify' Claude skill is a specialized tool for technical refinement, designed to distill complex codebases, system architectures, and technical documentation into their most essential forms. By utilizing advanced heuristics such as subtractive iteration, forced constraints, and complexity audits, it enables developers and architects to reduce technical debt and improve maintainability while ensuring that the core 'essence' and functionality of the solution remain intact.
Use Cases
- Code Refactoring: Streamline over-engineered functions or modules by applying subtractive iteration to remove redundant logic without breaking core features.
- Architectural Optimization: Conduct a 'Reverse Complexity Audit' on system designs to identify and eliminate unnecessary abstractions that increase maintenance overhead.
- Technical Documentation Simplification: Transform dense, jargon-heavy technical manuals into clear and concise guides using the 'Explain to Caveman' heuristic.
- Legacy System Modernization: Use the 'Rewrite Bet' strategy to identify the absolute minimum requirements and critical components when planning a migration from legacy systems.
- Constraint-Based Development: Re-implement existing solutions under strict line-of-code constraints to discover more efficient and elegant implementation patterns.
| name | simplify |
|---|---|
| description | When a solution needs simplifying, load this skill with the map-reduce skill to find its essence. |
::input::
$target: what to simplify $essence: what must be preserved
::context::
$relevantHeuristics: a list of heuristics picked from #heuristics
::workflow::
FOR $heuristic IN $relevantHeuristics Apply to $target Check if $essence is preserved IF simpler and essence intact THEN Keep the change END END
Heuristics
- Subtractive Iteration: remove one element and check if it still works.
- Forced Constraints: reimplement with half the lines and note what survives.
- Explain to Caveman: if you can't explain it simply, simplify it.
- Reverse Complexity Audit: list every abstraction and name the catastrophe it prevents.
- Rewrite Bet: two hours to rewrite from scratch, note what you keep.