Skip to content

DangQuangSE/team-development-skills / .agents/skills/problem-solving/collision-zone-thinking

Collision-Zone Thinking

Verified

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

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
AuthorizationBorder controlZero-trust, least privilege, audit logs
CachingHuman memoryForgetting curves, tiered memory (L1/L2/L3)

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

Best Source Domains for Collisions

  • Physics (thermodynamics, electrical, fluid dynamics)
  • Biology (evolution, immune system, neural networks)
  • Economics (supply/demand, markets, incentives)
  • Psychology (cognitive load, memory, attention)
  • Urban planning (traffic flow, zoning, infrastructure)

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)
  • The goal is insight extraction, not perfect metaphor
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 197kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall