akornmeier/Simplification Cascades
skills/problem-solving/simplification-cascades/SKILL.md
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
$ install --global
skillsauthnpx skillsauth add akornmeier/claude-config Simplification CascadesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 11:46 PM57.1s1 file scanned
SKILL.md
- 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?"
Related Skills
akornmeier/ux-spec-to-prompts
tools
VerifiedTrustedCommunity
Use when translating UX specifications into build-order prompts for UI generation tools. Triggers when user has a UX spec, PRD, or detailed feature doc and needs sequential, self-contained prompts for tools like v0, Bolt, or Claude frontend-design.
4SKILL.mdUpdated Apr 1, 2026
akornmeier/turborepo
development
VerifiedTrustedCommunity
Guide for implementing Turborepo - a high-performance build system for JavaScript and TypeScript monorepos. Use when setting up monorepos, optimizing build performance, implementing task pipelines, configuring caching strategies, or orchestrating tasks across multiple packages.
4SKILL.mdUpdated Apr 1, 2026
akornmeier/template-skill
tools
VerifiedTrustedCommunity
Replace with description of the skill and when Claude should use it.
4SKILL.mdUpdated Apr 1, 2026
akornmeier/tailwindcss
tools
VerifiedTrustedCommunity
Guide for implementing Tailwind CSS - a utility-first CSS framework for rapid UI development. Use when styling applications with responsive design, dark mode, custom themes, or building design systems with Tailwind's utility classes.
4SKILL.mdUpdated Apr 1, 2026