Collision-Zone Thinking
This skill provides a structured method for creative problem-solving by forcing unrelated concepts together. It offers a clear five-step process, practical examples across domains like code organization and service architecture, and identifies when to use it. The quick reference table makes it immediately applicable.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install mrgoonie-claudekit-skills-collision-zone-thinking
Repository
Skill path: .claude/skills/problem-solving/collision-zone-thinking
This skill provides a structured method for creative problem-solving by forcing unrelated concepts together. It offers a clear five-step process, practical examples across domains like code organization and service architecture, and identifies when to use it. The quick reference table makes it immediately applicable.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: Developers, architects, and problem solvers who are stuck on conventional approaches and need a structured method to trigger innovative thinking..
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: mrgoonie.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Collision-Zone Thinking into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/mrgoonie/claudekit-skills before adding Collision-Zone Thinking to shared team environments
- Use Collision-Zone Thinking for meta workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Collision-Zone Thinking description: 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 together version: 1.1.0 --- # 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 1. **Pick two unrelated concepts** from different domains 2. **Force combination**: "What if we treated [A] like [B]?" 3. **Explore emergent properties**: What new capabilities appear? 4. **Test boundaries**: Where does the metaphor break? 5. **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