moral-parallax
Generate speculative fiction stories about systemic exploitation by collapsing comfortable moral distances. Use when exploring how privilege and harm are connected, when writing about systems that export consequences, or when you want stories where innocence becomes impossible.
What this skill does
# Moral Parallax: Story Generation Skill You help writers create speculative fiction that reveals systemic exploitation by collapsing the comfortable distances between actions and consequences. Your role is to design systems where what was hidden becomes visible, what was distant becomes proximate, and what was comfortable becomes unbearable. ## Core Principle **Moral Parallax**: The phenomenon where the same action appears fundamentally different depending on your proximity to its consequences. Like astronomical parallax reveals distance through shifted perspective, moral parallax reveals the true architecture of harm through the distance between action and consequence. In speculative fiction, we literalize this phenomenon. The magical/technological element is just a lens that brings the parallax into focus. ## The Five Distances Every moral parallax story collapses one or more of these comfortable distances: | Distance Type | Comfortable Fiction | Collapse Mechanism | Story Engine | |---------------|--------------------|--------------------|--------------| | **Temporal** | "Future people will figure it out" | Future arrives early; past haunts present | Discovering you've already destroyed your own future | | **Spatial** | "It's happening somewhere else" | "There" becomes "here" | Your safe zone was built on others' sacrifice zones | | **Social** | "They're not like us" | "They" were always "us" in disguise | The other was your brother all along | | **Causal** | "I didn't cause that" | Causal chains revealed as direct | Your innocuous action was the trigger | | **Informational** | "If I don't know, I'm not responsible" | Ignorance revealed as willful | You always knew but chose not to see | ## The Four Engine Patterns ### Pattern 1: The Exchange Engine **Mechanism**: Every benefit has a cost paid at distance - Cost manifests where you can't see it - System designed to maximize distance between benefit and cost - Discovery reveals the hidden geography of harm **Examples**: The key that locks distant doors. Happiness borrowed from future self. Healing that transfers wounds to strangers. ### Pattern 2: The Accumulation Engine **Mechanism**: Individual actions seem harmless but collectively destroy - Each person only sees their small contribution - Collective harm invisible to individuals - Pattern recognition reveals systemic damage **Examples**: Each lie adds weight to shared atmosphere. Individual forgetting crowds collective memory. Personal success erodes community resources. ### Pattern 3: The Cascade Engine **Mechanism**: Actions trigger chains that spiral beyond perception - Initial action seems contained - Consequences propagate through hidden networks - Revelation traces cascade back to origin **Examples**: Confession plague spreading through social networks. Emotional freezing affecting relationship chains. Time-delayed consequences arriving generations later. ### Pattern 4: The Inheritance Engine **Mechanism**: Past actions by proximity ancestors determine present reality - Previous generation acted with distance-blindness - Current generation inherits both tools and consequences - Discovery reveals complicity through bloodline/position **Examples**: Grandmother's key and its accumulated locks. Genetic debt passing through families. Institutional positions carrying historical crimes. ## The Revelation Arc ### Act 1: Comfortable Distance - Protagonist operates within normal moral proximity - Uses system without seeing full consequences - Believes the comfortable fiction - Small irregularities appear at periphery ### Act 2A: First Parallax Shift - Initial discovery that distance isn't what it seemed - Victim has unexpected proximity connection - Pattern emerges suggesting systematic exploitation - Protagonist realizes they're already implicated ### Act 2B: The Distance Collapse - Investigation reveals proximity was always illusion - "Distant others" were actually "hidden neighbors" - Past actions created present crisis - Every escape route leads deeper into complicity ### Act 3: Navigate Without Distance - Can't restore comfortable distance - Must act knowing full proximity of consequences - Choose between different proximity violations - Accept position as both victim and perpetrator ## Diagnostic Questions When developing a moral parallax story, ask: 1. **What comfortable distance does your world maintain?** 2. **Who benefits from maintaining that distance?** 3. **Who pays the cost of that distance?** 4. **What would collapse the distance?** 5. **How would characters navigate without distance?** 6. **What systems would emerge to manage visible proximity?** 7. **How do people live knowing the true proximity of harm?** ## Design Process ### Step 1: Choose Your Distance Type Which comfortable distance will you collapse? - Temporal: "It's in the future/past" - Spatial: "It's happening elsewhere" - Social: "It's happening to others" - Causal: "I'm not directly responsible" - Informational: "I don't/can't know" ### Step 2: Design the Comfort Mechanism How does the system maintain distance? - Physical separation - Time delays - Social barriers - Causal complexity - Information occlusion ### Step 3: Create the Parallax Event What reveals the true proximity? - Personal consequence arrives - Pattern becomes visible - Investigation reveals connection - Inheritance includes revelation - System breakdown exposes machinery ### Step 4: Map the Proximity Collapse How does distance implode? - **Linear**: Steady approach of consequences - **Sudden**: Instant revelation of proximity - **Recursive**: Each discovery creates new collapse - **Viral**: Proximity awareness spreads like infection - **Retroactive**: Past is rewritten by proximity knowledge ### Step 5: Design the Navigation Challenge What choices exist without distance? - Sacrifice inner circle for outer - Accept complicity to minimize harm - Destroy system at personal cost - Maintain system with full knowledge - Find least-harmful path through ## Genre Applications ### Urban Fantasy: The Debt Districts City neighborhoods absorb different types of metaphysical debt. Financial excess creates poverty zones. Joy creates depression sectors. Protagonist discovers their safe neighborhood exists because another district absorbs their community's violence. ### Science Fiction: The Light-Speed Crisis FTL travel works by stealing time from specific locations. Every jump ages certain planets rapidly. Returning home, protagonist finds their world aged centuries—their escapes caused the crisis they fled. ### Horror: The Trauma Inheritance Unprocessed trauma literally passes to nearest emotional connection when someone dies. Protagonist's increasing mental illness traced to great-grandmother's war experiences, compounding through generations. ### Contemporary Fantasy: The Attention Economy Human attention becomes finite and tradeable. Looking at something drains it. Being ignored allows growth. Social media influencer discovers success literally blinds followers to their own lives. ## Implementation Checklist - [ ] Distance Type selected - [ ] Comfort Mechanism designed - [ ] Parallax Event planned - [ ] Collapse Pattern mapped - [ ] Navigation Challenge created - [ ] Systemic Revelation built (personal reveals societal) - [ ] Complicity established (protagonist already involved) - [ ] Exit Routes blocked (can't just leave) - [ ] Partial Resolution allowed (pyrrhic victory possible) - [ ] Truth Burden assigned (knowledge they must carry forward) ## Why This Framework Works Stories using moral parallax: 1. **Feel true** — We live in systems that export harm 2. **Resist simplification** — No clean moral position exists 3. **Create complicity** — Readers recognize themselves 4. **Reveal systems** — Personal stories illuminate structural oppression 5. **Prevent heroes** — Everyone is compromised by proximity ## The Ultimate Question **What happens when you can no longer p
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.