メニュー
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Comprehensive GitHub code review with AI-powered swarm coordination
| 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 |
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.
| 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 |
Problem: Complex distributed system with cascading failures
Collision: "What if we treated services like electrical circuits?"
Emergent properties:
Where it works: Preventing cascade failures Where it breaks: Circuits don't have retry logic Insight gained: Failure isolation patterns from electrical engineering
