d799284b15
The optional-skills copy was still the v1.0.0 constraint-dispatch skill (SKILL.md + full-prompt-library.md only). This brings it up to the current tool: a situation-routed library of 22 named ideation methods drawn from working artists, scientists, designers, and writers. SKILL.md becomes a 4-step router (extract PHASE/DOMAIN/SPECIFICITY signals → apply overrides → route phase-then-domain → resolve ambiguity), with anti-slop operating rules and an anti-default check. Adds: - 22 method files under references/methods/ — oblique-strategies (Eno/Schmidt), oulipo, scamper, lateral-provocations (de Bono), triz (Altshuller), leverage-points (Meadows), pattern-languages (Alexander), compression-progress (Schmidhuber), analogy-and-blending, pataphysics, first-principles, polya, biomimicry, volume-generation, creative-discipline, premortem-and-inversion, defamiliarization, derive-and-mapping, affinity-diagrams, jobs-to-be-done, story-skeletons, chance-and-remix. Each: when/when-not, the actual cards/principles/operators, a procedure, a worked example, anti-slop notes. - references/method-catalog.md (index + when-to-use), heuristics.md (extended decision tree), anti-slop.md (rules applied to every output), exercises.md (time-boxed exercises). - full-prompt-library.md restructured into domain-affinity sections (general / software / physical / social / lists) so the no-direction default isn't developer-biased. Frontmatter: name aligned to directory slug (creative-ideation, folding in the fix from #18084); version 2.0.0→2.1.0; platforms field preserved. Original wttdotm-derived constraint dispatch is kept as the default path. Supersedes #19295 (which targeted the pre-move skills/ path). Co-authored-by: SHL0MS <SHL0MS@users.noreply.github.com>
4.1 KiB
Defamiliarization
Two traditions naming the same operation: make the familiar strange.
- Viktor Shklovsky, 1917 — ostranenie. Russian Formalist core: art removes the perceptual automatism that makes familiar things invisible.
- Bertolt Brecht, 1930s — Verfremdungseffekt. Theatrical alienation effect, prevents emotional identification, enables critical distance.
Long predates either: Borges, Wittgenstein, nouveau roman (Robbe-Grillet), Calvino, much philosophical writing.
When to use
- Writing about something so familiar you've stopped seeing it (your neighborhood, your daily software, your institutional culture)
- Working on a problem in a domain you've internalized — the expert knows too much
- Producing critical writing — surface what is presented as natural
- User research / ethnography — describe what people do without importing their categories
- Stale on your own work — read it as if you'd never written it
Don't use when
- The reader doesn't have the familiar context (defamiliarizing the unfamiliar = incomprehensible)
- You need warm identifying engagement (Brecht's purpose is the opposite of identification)
- Producing transparent technical documentation
- Stuck because you don't yet understand the subject (need study, not estrangement)
Procedure
For writing
- Pick a familiar thing in your draft.
- Describe it from a position lacking the relevant idiom — a visiting alien, a child, a 17th-century person, a future archaeologist.
- Force only physical descriptions. No labels, no shortcuts, no idioms.
- Read the result. Note what you noticed that was previously invisible.
- Decide: keep the defamiliarized passage, or use it as research and rewrite the labeled version informed by it.
For analysis / critique
- Identify what's presented as natural in your subject.
- Defamiliarize that thing. Describe it without accepting its naturalness.
- The choices that produced the appearance of naturalness become visible.
For user research
Watch users do something everyone in your domain treats as obvious. Describe without domain vocabulary. Often reveals friction you'd long since rationalized.
Worked example
Subject: writing about software engineering as a profession.
Familiar version: "Software engineers write code, debug, and deploy systems. The work is mostly typing, with occasional meetings."
Defamiliarized: "Software engineers spend the largest part of their day moving small marks of light across glass surfaces by twitching their fingers. The marks form chains that, when read by certain machines elsewhere, cause the machines to perform actions the engineer has imagined. The engineer cannot directly observe most of the actions; they receive reports about what happened. A significant portion of their time is spent identifying differences between what they imagined and what was reported, and adjusting the marks to bring the reports closer to the imagination. Many of these adjustments are minute — single missing or extra marks. Engineers describe the activity using metaphors of building, despite producing no physical object."
The labeled version had hidden the mediation (engineers can't observe the thing they're making), the imagination-vs-report gap (most of debugging), the abstract-physical mismatch (they say "build" but make nothing material). All three are critically important features that disappear under labels.
Anti-slop notes
- "See X with fresh eyes" is a slogan, not a technique. Real defamiliarization uses specific operations — alien perspective, missing idiom, physical-only description.
- Don't fake by adding adjectives. Real defamiliarization removes labels, doesn't decorate them. "The great metal beast roared down the gleaming pathway" is purple prose, not defamiliarization.
- Use locally. Constant defamiliarization is exhausting and self-defeating. Apply where the familiar has gone invisible.
- Don't use as fashionable jargon. Use the operation; don't invoke the term unless discussing the tradition.
Sources: Shklovsky, "Art as Device" (1917); Brecht, "A Short Organum for the Theatre" (1948).