Start a fresh conversation. Replace the highlighted placeholders.
Use Collision-Zone Thinking to explore [problem] by treating it like [unrelated domain], then deliver novel solution ideas, where the metaphor breaks down, and the most useful insight.
Required inputs
[problem]
[unrelated domain]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: Collision-Zone Thinkingdescription: Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"when_to_use: when conventional approaches feel inadequate and you need breakthrough innovation by forcing unrelated concepts togetherversion: 1.1.0
Collision-Zone Thinking
Overview
Revolutionary insights come from forcing unrelated concepts to collide. Treat X like Y and see what emerges.
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