Collision-Zone Thinking
About
Collision-Zone Thinking is a technique for generating breakthrough innovation by forcing unrelated concepts together, such as treating code organization like DNA. It is best used when conventional approaches are inadequate and you need to discover novel, emergent solutions. The method works by deliberately mixing metaphors to reframe problems and unlock new perspectives.
Quick Install
Claude Code
Recommended/plugin add https://github.com/Elios-FPT/EliosCodePracticeServicegit clone https://github.com/Elios-FPT/EliosCodePracticeService.git ~/.claude/skills/Collision-Zone ThinkingCopy and paste this command in Claude Code to install this skill
Documentation
Collision-Zone Thinking
Overview
Revolutionary insights come from forcing unrelated concepts to collide. Treat X like Y and see what emerges.
Core principle: Deliberate metaphor-mixing generates novel solutions.
Quick Reference
| Stuck On | Try Treating As | Might Discover |
|---|---|---|
| Code organization | DNA/genetics | Mutation testing, evolutionary algorithms |
| Service architecture | Lego bricks | Composable microservices, plug-and-play |
| Data management | Water flow | Streaming, data lakes, flow-based systems |
| Request handling | Postal mail | Message queues, async processing |
| Error handling | Circuit breakers | Fault isolation, graceful degradation |
Process
- Pick two unrelated concepts from different domains
- Force combination: "What if we treated [A] like [B]?"
- Explore emergent properties: What new capabilities appear?
- Test boundaries: Where does the metaphor break?
- Extract insight: What did we learn?
Example Collision
Problem: Complex distributed system with cascading failures
Collision: "What if we treated services like electrical circuits?"
Emergent properties:
- Circuit breakers (disconnect on overload)
- Fuses (one-time failure protection)
- Ground faults (error isolation)
- Load balancing (current distribution)
Where it works: Preventing cascade failures Where it breaks: Circuits don't have retry logic Insight gained: Failure isolation patterns from electrical engineering
Red Flags You Need This
- "I've tried everything in this domain"
- Solutions feel incremental, not breakthrough
- Stuck in conventional thinking
- Need innovation, not optimization
Remember
- Wild combinations often yield best insights
- Test metaphor boundaries rigorously
- Document even failed collisions (they teach)
- Best source domains: physics, biology, economics, psychology
GitHub Repository
Related Skills
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
