Collision-Zone Thinking
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Best use case
Collision-Zone Thinking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Teams using Collision-Zone Thinking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/collision-zone-thinking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Collision-Zone Thinking Compares
| Feature / Agent | Collision-Zone Thinking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review writing use peer-review.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-asset-generator
Generate web assets including favicons, app icons (PWA), and social media meta images (Open Graph) for Facebook, Twitter, WhatsApp, and LinkedIn. Use when users need icons, favicons, social sharing images, or Open Graph images from logos or text slogans. Handles image resizing, text-to-image generation, and provides proper HTML meta tags.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
variant-analysis
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.
wycheproof
Wycheproof provides test vectors for validating cryptographic implementations. Use when testing crypto code for known attacks and edge cases.
testing-handbook-generator
Meta-skill that analyzes the Trail of Bits Testing Handbook (appsec.guide) and generates Claude Code skills for security testing tools and techniques. Use when creating new skills based on handbook content.
ruzzy
Ruzzy is a coverage-guided Ruby fuzzer by Trail of Bits. Use for fuzzing pure Ruby code and Ruby C extensions.
ossfuzz
OSS-Fuzz provides free continuous fuzzing for open source projects. Use when setting up continuous fuzzing infrastructure or enrolling projects.
libfuzzer
Coverage-guided fuzzer built into LLVM for C/C++ projects. Use for fuzzing C/C++ code that can be compiled with Clang.
libafl
LibAFL is a modular fuzzing library for building custom fuzzers. Use for advanced fuzzing needs, custom mutators, or non-standard fuzzing targets.
harness-writing
Techniques for writing effective fuzzing harnesses across languages. Use when creating new fuzz targets or improving existing harness code.