MCP HubMCP Hub
スキル一覧に戻る

Collision-Zone Thinking

Elios-FPT
更新日 Today
196 閲覧
1
GitHubで表示
その他general

について

衝突領域思考(コリジョン・ゾーン・シンキング)は、コードの構造をDNAのように扱うといった、無関係な概念を強制的に結びつけることで画期的なイノベーションを生み出す手法です。従来の手法が不十分で、新奇な創発的解決策を見出す必要がある場合に最適です。この方法は、比喩を意図的に混合して問題を再定義し、新たな視点を解き放つことで効果を発揮します。

クイックインストール

Claude Code

推奨
プラグインコマンド推奨
/plugin add https://github.com/Elios-FPT/EliosCodePracticeService
Git クローン代替
git clone https://github.com/Elios-FPT/EliosCodePracticeService.git ~/.claude/skills/Collision-Zone Thinking

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

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 OnTry Treating AsMight Discover
Code organizationDNA/geneticsMutation testing, evolutionary algorithms
Service architectureLego bricksComposable microservices, plug-and-play
Data managementWater flowStreaming, data lakes, flow-based systems
Request handlingPostal mailMessage queues, async processing
Error handlingCircuit breakersFault 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

GitHub リポジトリ

Elios-FPT/EliosCodePracticeService
パス: .claude/skills/problem-solving/collision-zone-thinking

関連スキル

algorithmic-art

メタ

This Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.

スキルを見る

subagent-driven-development

開発

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

スキルを見る

executing-plans

デザイン

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

スキルを見る

cost-optimization

その他

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

スキルを見る