Agent Skills › mrgoonie/claudekit-skills › Collision-Zone Thinking

Collision-Zone Thinking

GitHub

一种通过强制组合不相关概念来激发创新思维的认知技巧，旨在突破常规思维定势，发现涌现性解决方案。

.claude/skills/problem-solving/collision-zone-thinking/SKILL.md mrgoonie/claudekit-skills

Trigger Scenarios

遇到技术瓶颈无法突破需要非渐进式创新方案思维陷入常规模式

Install

npx skills add mrgoonie/claudekit-skills --skill Collision-Zone Thinking -g -y

More Options

Non-standard path

npx skills add https://github.com/mrgoonie/claudekit-skills/tree/main/.claude/skills/problem-solving/collision-zone-thinking -g -y

Use without installing

npx skills use mrgoonie/claudekit-skills@Collision-Zone Thinking

指定 Agent (Claude Code)

npx skills add mrgoonie/claudekit-skills --skill Collision-Zone Thinking -a claude-code -g -y

安装 repo 全部 skill

npx skills add mrgoonie/claudekit-skills --all -g -y

预览 repo 内 skill

npx skills add mrgoonie/claudekit-skills --list

SKILL.md

Frontmatter

{
    "name": "Collision-Zone Thinking",
    "version": "1.1.0",
    "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"
}

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