bisociative-creativity
Bisociative Creativity
Core principle: Creativity is not randomness. It is the discovery of a hidden connection between two frames of reference that don't normally touch. Arthur Koestler called this bisociation — the moment when two independent "matrices of thought" collide and produce something that belongs to neither but couldn't exist without both.
A joke, a scientific breakthrough, and an artistic insight share the same structure: two planes of meaning intersect at a point that surprises.
LLMs are powerful associative machines but default to mode-seeking — the statistically most likely continuation. Creativity is, almost by definition, off the mode. This skill is a systematic protocol for forcing the model off its default gradient and into productive collision space.
What Makes This Different
| Skill | Purpose | This skill's distinction |
|---|---|---|
| lateral-thinking | Escape a dominant pattern when stuck | Not stuck — generating from scratch |
| analogical-thinking | Transfer structural solutions across domains | Not solving a problem — producing novel ideas |
| bisociative-creativity | Collide unrelated frames to generate genuinely novel output | Creative generation as the primary goal |
Use this skill when the deliverable is an idea, not a diagnosis or a decision.
The Bisociation Engine
Phase 1 — Frame Selection (Divergent)
The quality of bisociative output depends entirely on the quality and distance of the frames collided. Close frames produce incremental ideas. Distant frames produce surprising ones.
Step 1: Name the seed domain State the topic or brief for which ideas are needed:
- "Conference talk titles about context engineering"
- "Product names for a visual knowledge mapping tool"
- "Marketing angle for an AI-powered restaurant platform"
Step 2: Generate 5–7 distant frames Select frames that have no obvious connection to the seed domain. Distance is the critical variable — the further the better. Use these generators:
| Generator | Method | Example (seed: "context engineering for AI agents") |
|---|---|---|
| Sensory world | Pick a physical material, texture, or natural process | Mycelium networks, tidal erosion, fermentation |
| Historical era | Pick a non-obvious historical period or event | Venetian glassmaking guilds, the Rosetta Stone decipherment |
| Art form | Pick a creative discipline far from the seed | Butoh dance, mosaic restoration, jazz comping |
| Everyday ritual | Pick a mundane human activity | Packing a suitcase, mise en place, tuning a guitar |
| Unrelated industry | Pick a field with zero surface overlap | Perfumery, air traffic control, wine terroir |
| Emotional state | Pick a specific human feeling or experience | The moment before a sneeze, homesickness, flow state |
| Constraint injection | Impose an arbitrary rule from another domain | "What if context had an expiry date like fresh produce?" |
Rules for frame selection:
- If you can immediately see the connection, the frame is too close — pick a more distant one
- At least 2 frames should feel genuinely absurd or uncomfortable
- Never pick frames that are common metaphors for the seed (e.g., don't pick "orchestra conductor" for "team leadership" — that's a dead metaphor)
Phase 2 — Collision (the creative act)
For each frame, force a collision with the seed domain. This is not metaphor-making — it is structural interrogation.
For each frame, ask these questions in order:
- What is the core mechanic of this frame? (How does it actually work, physically or conceptually?)
- What tensions or trade-offs exist inside this frame? (What does it balance? What can go wrong?)
- Where does the structure of this frame intersect the structure of the seed? (Find the non-obvious overlap — the bisociation point)
- What idea does the collision produce? (State it as a concrete concept, not an abstract connection)
Critical rule: Do not filter during collision. Every collision gets written down. Judgment happens in Phase 3, never in Phase 2. Premature convergence is the #1 killer of creative output.
Example collision:
- Seed: product name for visual knowledge mapping tool
- Frame: fermentation
- Mechanic: Transformation over time; raw inputs become something new through controlled conditions; the process itself adds value
- Tensions: Speed vs. depth; control vs. wild cultures; surface scum hides productive transformation below
- Bisociation point: Knowledge isn't organized — it develops. The tool doesn't map what you know; it lets ideas ferment into structure
- Ideas produced: "Kultur" (double meaning), "Starter" (sourdough starter = knowledge starter), a tagline: "Let your ideas develop"
Phase 3 — Harvest (Convergent)
Now — and only now — apply judgment.
Triage every idea into one of three buckets:
| Bucket | Criteria | Action |
|---|---|---|
| 🔥 Live spark | Surprising AND structurally sound — the connection is real, not forced | Develop immediately |
| 🌱 Kernel | The idea itself is impractical, but there's a usable concept buried inside | Extract the kernel, restate it, look for a better vehicle |
| 💀 Dead end | Forced, generic, or the connection only works if you squint | Discard without guilt |
For each live spark, develop it:
- State the idea in one sentence
- Explain the bisociation: what two frames collided and why it works
- Give 2–3 variations or extensions
- Identify the strongest single expression of the idea
For each kernel, extract and re-plant:
- What's the usable concept?
- Can it be combined with another kernel or spark?
- Try colliding the kernel with a different frame from Phase 1
Output Format
🎯 Creative Brief
Restate the seed domain and what kind of ideas are needed (names, concepts, angles, themes, etc.)
🔀 Frame Selection
List the 5–7 distant frames chosen, with a one-line note on why each was selected (distance justification).
💥 Collisions
For each frame:
- Frame × Seed: [frame name]
- Core mechanic: [how the frame works]
- Bisociation point: [where the structures intersect]
- Ideas produced: [concrete ideas — plural]
🔥 Live Sparks
The 3–5 strongest ideas, each with:
- The idea in one sentence
- Why it works (the collision that produced it)
- 2–3 variations
- Strongest single expression
🌱 Kernels Worth Saving
Concepts extracted from weaker collisions that may be useful later or in combination.
Oblique Strategy Injections
When the collision phase feels mechanical or the sparks aren't firing, inject one of these meta-provocations to destabilize the process itself:
- "What if the opposite of this idea were the idea?"
- "What would make someone laugh about this?"
- "What would this be if it were a sound? A smell? A temperature?"
- "What's the version of this that would get you fired?"
- "What's the version of this that a 6-year-old would invent?"
- "Honor thy error as a hidden intention" — if a collision produced something unintended, follow that instead
- "What would this look like in 1926? In 2126?"
- "Remove the most important element. What's left?"
These are escape hatches from the protocol itself — use them when the process becomes the rut.
Anti-Patterns (How Creative Generation Fails)
| Anti-pattern | Symptom | Fix |
|---|---|---|
| Mode-seeking | All ideas sound like what a "creative AI" would say | Increase frame distance; add constraint injection |
| Dead metaphor | Using tired comparisons (journey, tapestry, compass) | Reject any frame that's already a cliché for the seed |
| Premature convergence | Filtering during Phase 2 | Enforce the rule: no judgment until Phase 3 |
| Surface bisociation | Connection is wordplay, not structural | Ask "does this work if I remove the pun?" — if not, dig deeper |
| Quantity collapse | Stopping at 3 ideas because they feel "good enough" | Set a quota before starting (minimum 15 raw ideas across all frames) |
| Comfort zone frames | All selected frames are adjacent to the seed | Mandate at least 2 frames from sensory/emotional/everyday generators |
Recombination Protocol
After the initial harvest, try cross-pollinating between sparks:
- Take your top 3 live sparks
- Ask: "What if Spark A and Spark B were the same idea?"
- Force the combination — don't ask if it makes sense yet
- Often the best idea in the session comes from a second-order collision: two bisociations bisociating
Calibrating for Different Creative Tasks
| Task type | Frame distance | Collision depth | Output style |
|---|---|---|---|
| Naming (products, projects) | Maximum — absurd frames welcome | Focus on sound, rhythm, double meaning | Short, punchy, memorable |
| Concepts (product ideas, features) | High — cross-industry | Focus on mechanics and user experience | Functional description + emotional hook |
| Writing angles (talks, posts, essays) | Medium-high — surprising but graspable | Focus on narrative tension and audience surprise | Thesis + opening line |
| Visual concepts (design, branding) | Maximum — synesthetic frames encouraged | Focus on sensory overlap and spatial metaphor | Image description + mood |
| Strategy / positioning | Medium — credible but differentiated | Focus on competitive contrast and audience psychology | One-line positioning + why it's defensible |
Thinking Triggers
- "What two things that have never been combined would produce this?"
- "What frame would make an expert in [seed domain] uncomfortable?"
- "What's the version of this idea that doesn't exist yet because no one thought to connect these two worlds?"
- "If I couldn't use any word associated with [seed domain], how would I describe this?"
- "What would someone from [random profession] find interesting about this problem?"
Example Applications
- "I need a name for my open-source context management standard" → Collide with: cartography, mycology, textile weaving, astronomical navigation, culinary mise en place → produce 15+ candidates, harvest the sparks
- "Give me a fresh angle for my conference talk" → Collide the thesis with: sommelier wine service, emergency room triage, darkroom photography development, archaeological stratigraphy → find the metaphor that makes the audience see the idea differently
- "I want creative ideas for a team offsite" → Collide "team alignment" with: improv theater, foraging, radio astronomy, bread baking, orienteering → produce activity concepts that embody the goal rather than just discussing it
- "Help me brainstorm marketing angles" → Collide product value prop with: magician's misdirection, geological sedimentation, DJ mixing, mapmaking, sourdough → find the angle that competitors can't copy because it comes from a unique frame
More from andurilcode/craftwork
deep-document-processor
>
4summarizer
Apply this skill whenever the user asks to summarize, condense, distill, or compress any content — a document, article, meeting notes, conversation, codebase, book, research paper, video transcript, or any other source material. Triggers on phrases like 'summarize this', 'give me the TL;DR', 'condense this', 'what are the key points?', 'distill this down', 'brief me on this', 'what's the gist?', 'BLUF this', 'executive summary', 'compress this for me', or any request to reduce content while preserving its essential value. Also trigger when the user pastes a long text and implicitly wants it shortened, when they share a link and ask 'what does this say?', or when they ask for meeting notes or action items from a transcript. This skill does NOT apply to 'explain X to me' (use topic-explainer) or 'write a summary section for my doc' (use technical-writing). This skill is for when source material exists and needs to be compressed.
3inversion-premortem
Apply inversion and pre-mortem thinking whenever the user asks to evaluate a plan, strategy, architecture, feature, or decision before execution — or when they want to stress-test something that already exists. Triggers on phrases like "is this a good idea?", "what could go wrong?", "review this plan", "should we do this?", "are we missing anything?", "stress-test this", "what are the risks?", or any request to validate a decision or design. Use this skill proactively — if the user is about to commit to something, this skill should be consulted even if they don't ask for it explicitly.
3llms-txt-generator
Generate llms.txt-style context documents — token-budgeted, section-per-concept Markdown optimized for LLM and RAG consumption. Use this skill whenever someone asks to generate an llms.txt, create LLM-friendly documentation, produce a context document for a library or codebase, build a RAG-ready reference, make docs 'agent-readable', create a developer quick-reference, or says anything like 'generate context for X', 'make an llms.txt for this repo', 'create a reference doc for NotebookLM', 'turn these docs into something an LLM can use', 'context document', 'developer cheatsheet from docs'. Also trigger when someone provides a GitHub repo URL and asks for documentation synthesis, or when working inside a codebase and asked to produce a self-contained reference of how it works. This is the context engineer's doc generation tool — it turns sprawling documentation into precise, structured, token-efficient context.
3context-compressor
>
3probabilistic-thinking
Apply probabilistic and Bayesian thinking whenever the user needs to reason under uncertainty, compare risks, prioritize between options, update beliefs based on new evidence, or make decisions without complete information. Triggers on phrases like "what are the odds?", "how likely is this?", "should I be worried about X?", "which risk is bigger?", "does this data change anything?", "is this a signal or noise?", "what's the probability?", "how confident are we?", or any situation where decisions are being made based on incomplete or ambiguous evidence. Also trigger when someone is treating uncertain outcomes as certainties, or when probability language is being used loosely ("probably", "unlikely", "very likely") without quantification. Don't leave uncertainty unexamined.
3