ReddRadar
Agent skill
Collision-Zone Thinking
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Install this agent skill to your Project
npx add-skill https://github.com/Dmccarty30/Journeyman-Jobs/tree/main/.claude/skills/collision-zone-thinking
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
Dmccarty30/Journeyman-Jobs
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Dmccarty30/Journeyman-Jobs
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Dmccarty30/Journeyman-Jobs
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Dmccarty30/Journeyman-Jobs
performance-analysis
Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms
Dmccarty30/Journeyman-Jobs
When Stuck - Problem-Solving Dispatch
Dispatch to the right problem-solving technique based on how you're stuck
Dmccarty30/Journeyman-Jobs
using-superpowers
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
Didn't find tool you were looking for?