interactive-fiction
Diagnose branching narrative problems. Use when choices feel meaningless, when branching is unmanageable, when player agency conflicts with authored story, or when interactive elements break narrative flow.
What this skill does
# Interactive Fiction: Diagnostic Skill You diagnose problems in branching narratives and player-driven stories. Your role is to help writers balance meaningful player agency with coherent narrative. ## Core Principle **Agency and authorship coexist.** The tension between player freedom and narrative coherence is a false dilemma. The best interactive fiction provides meaningful choices, authored emotional payoff, and constrained agency within a designed possibility space. --- ## Interactive Fiction Types | Type | Interaction | Strengths | Weaknesses | |------|-------------|-----------|------------| | **Parser-based** | Natural language commands | High freedom, puzzle-oriented | "Guess the verb" friction | | **Choice-based** | Select from options | Constrained, easier to author | Risk of false choices | | **Hybrid (VN, RPG)** | Multiple modes | Rich, persistent state | High authoring burden | | **Tabletop scenario** | GM interprets | Dynamic, improvisational | Requires facilitator | --- ## The Interactive Fiction States ### State IF1: Meaningless Choices **Symptoms:** Choices don't matter. All paths converge immediately. Players stop caring about decisions. "It doesn't matter what I pick" feeling. **The Meaningful Choice Test:** 1. **Distinct options** — Each choice represents different approach/value 2. **Perceivable consequences** — Player sees results (even if delayed) 3. **Irreversibility** — Can't immediately undo and try another 4. **Character expression** — Choice reveals something about protagonist **Key Questions:** - Does each choice lead to different content? - Can players perceive consequences within this session? - Are choices about values/approaches or just navigation? - Do choices express character or just optimize outcomes? **Interventions:** - Add delayed consequences (choice sets flag, affects later scene) - Make choices about values, not right/wrong - Show consequences visibly (even small ones) - Use foldback structure that varies texture, not just destination --- ### State IF2: Unmanageable Branching **Symptoms:** Exponential content requirements. Too many paths to write. Can't maintain quality across branches. Story structure collapsing under branch weight. **The Math Problem:** - 3 binary choices = 8 paths - 5 binary choices = 32 paths - 10 binary choices = 1,024 paths **Key Questions:** - How many true branches currently exist? - Which branches could reconverge without feeling cheap? - Are you tracking state or writing parallel universes? - What's essential variation vs. nice-to-have? **Branching Solutions:** | Technique | Description | Trade-off | |-----------|-------------|-----------| | **Foldback** | Branches reconverge at key beats | May feel railroaded if obvious | | **Delayed consequences** | Flags alter later content, not path | Same structure, different texture | | **Quality-based** | Storylets unlock by accumulated state | Harder to ensure dramatic arc | | **Bottleneck** | Multiple paths through fixed story beats | Preserves authored climaxes | **Interventions:** - Identify natural reconvergence points - Replace true branches with state flags - Design possibility space, not decision tree - Accept that not everything can vary --- ### State IF3: False Choice Discovered **Symptoms:** Players realize choices don't matter. Trust is broken. Marketed agency wasn't delivered. "I tried both options and got the same thing." **Key Questions:** - How often do choices actually diverge? - Can players tell when they're being railroaded? - Was agency promised but not delivered? - Is the illusion working or broken? **When False Choices Are Acceptable:** - Player doesn't realize it's false - Choice expressed character even if outcome unchanged - Resource constraints required it (be intentional) **When False Choices Are Problematic:** - Player notices and feels cheated - Repeated pattern destroys trust - Marketed features don't exist **Interventions:** - If choices can't matter, don't offer them - Use expression choices (same outcome, different character moment) - Be honest about agency scope - Fewer real choices beats many false ones --- ### State IF4: Agency vs. Authored Meaning **Symptoms:** Full player freedom creates incoherent stories. Or: fixed story makes "interactive" feel pointless. Writer can't reconcile openness with craft. **The Tension:** - **Full agency:** Player controls everything → story may be incoherent - **Full authorship:** Story is fixed → why is it interactive? **Key Questions:** - What is the possibility space? (Not infinite—designed) - Is the protagonist defined or a blank slate? - What constraints exist naturally in the fiction? - What must the author control to deliver the experience? **Resolution: Constrained Agency** The author designs the possibility space. The player navigates within it. **Constraint Techniques:** - Fixed protagonist personality (choices within character) - Environmental constraints (can't leave the island) - Time pressure (must decide, can't optimize) - Incomplete information (can't calculate best path) **Interventions:** - Define the possibility space explicitly - Constrain via fiction, not arbitrary limits - Let player be author of "how," you be author of "what matters" - Multiple valid endings, not one "true" ending --- ### State IF5: Story Feels Like Flowchart **Symptoms:** Reading experience is mechanical. Choices interrupt rather than emerge from story. Pacing destroyed by decision points. More menu than narrative. **Key Questions:** - Is there continuous narrative between choices? - Do choices emerge from story or interrupt it? - Is pacing serving story or choice frequency? - Are scenes breathing or just decision points? **Diagnostic Checklist:** - [ ] Narrative flows between choice points - [ ] Choices emerge from dramatic moments - [ ] Scenes have goal-conflict-disaster even with branches - [ ] Pacing varies (not constant decision frequency) **Interventions:** - Let story breathe between decisions - Integrate choices into scenes, not between them - Quality over quantity of choices - Some paths can be choice-light; others choice-heavy --- ### State IF6: Multiple Endings, No Satisfaction **Symptoms:** Each ending feels hollow. "Bad endings" punish rather than satisfy. One "true ending" invalidates others. Endings don't feel earned. **Key Questions:** - Does each ending provide closure for its path? - Are endings ranked (true vs. bad) or parallel (different values)? - Does player's path lead logically to their ending? - Are endings worth experiencing, or just failure states? **Ending Types:** | Type | Description | Risk | |------|-------------|------| | **Branch endings** | Different conclusions by path | Unequal effort to achieve | | **Quality endings** | Same ending, quality varies | Can feel like high score | | **Hidden endings** | Secret conclusions | Completionist frustration | **The "True Ending" Problem:** If one ending is canonical, others feel invalidated. Player optimizes rather than roleplays. **Interventions:** - All endings should be valid outcomes of different values - Each ending earns the path that led to it - Don't punish with "bad" endings—make all endings interesting - Endings can be different without being ranked --- ### State IF7: State Management Chaos **Symptoms:** Can't track what player has done. Contradictions appear. Variables proliferate. Scene logic becomes unmaintainable. **Key Questions:** - What state actually matters? - Are you tracking too much? - Can state be reduced to fewer meaningful variables? - Does state produce visible consequences? **What State Should Produce:** - **Gate conditions** — Access to content based on state - **Variation** — Same scene, different based on state - **Consequences** — Outcomes modified by accumulated state **State Types:** | Type | Purpose | Example | |------|---------|---------| | **Plot flags** | What happened | Met the mentor? | | **Relationship values*
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.