Claude Cursor opencode Skill

Collision-Zone Thinking

Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download vodailocz-kilo-kit-mcp-skills_problem-solving_collision-zone-thinking-0448e6c.zip · 1 KB
Part of vodailocz/kilo-kit-mcp — 142 skills

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/problem-solving/collision-zone-thinking
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (kilo-kit-mcp)
  • SKILL.md 2.2 KB
    ---
    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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related