[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJPRD5EHGZ5BQZ7FSX6SCW":3,"skill-same:01M7EJPRD5EHGZ5BQZ7FSX6SCW":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M7EJPRD5EHGZ5BQZ7FSX6SCW","game-storytelling",null,"Use when a game's story is the work: premise and pillars, branching topology, meaningful choice, dialogue state, quests, environmental storytelling, ludonarrative harmony. Author portable — engine wiring is `godot`\u002F`unity`\u002F`unreal`. NOT the mechanics and economy the story serves (that is `game-design`), NOT level layout (that is `level-design`).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game-storytelling\ndescription: \"Use when a game's story is the work: premise and pillars, branching topology, meaningful choice, dialogue state, quests, environmental storytelling, ludonarrative harmony. Author portable — engine wiring is `godot`\u002F`unity`\u002F`unreal`. NOT the mechanics and economy the story serves (that is `game-design`), NOT level layout (that is `level-design`).\"\ntags: [game, narrative, story, dialogue, quest, branching, worldbuilding]\nrecommends: [game-design, level-design]\nprofiles: [full]\norigin: risco\n---\n\n# Game Storytelling — Narrative Design (engine-agnostic)\n\n*Design the story as a system the player operates, not a script they watch. This skill owns the narrative graph — premise, pillars, branches, choices, dialogue state, quests, and the storytelling embedded in the world.*\n\nYou produce **design artifacts**: a premise\u002Ftheme\u002Fpillars doc, a branch topology, a state\u002Fflag table, dialogue in a portable format (Ink\u002FYarn\u002FTwee\u002Farticy), quest specs, and environmental beats. Story is a **system in service of play**; when you catch yourself designing a great scene the mechanics can't honor, reconcile it (see Ludonarrative harmony) rather than ship the dissonance.\n\nBoundaries: **game-design** owns what the player *does* — core loop, verbs, systems, progression, economy, difficulty, balance — and the story serves those verbs; call it when resolving dissonance needs a *mechanic* change, or when designing the conditions for systemic\u002Femergent story. **level-design** owns spatial layout, encounter placement, sightlines, blockout and the pacing *of a space* — the space environmental storytelling lives inside; co-own the set-dressing. **godot \u002F unity \u002F unreal** implement the dialogue runner, quest state, save-serialization of story state, and the Ink\u002FYarn\u002Farticy plugin glue — author portable, they wire it. **marketing** owns the store page, premise pitch and trailer copy (external-facing, not in-game narrative). Prose fiction, a screenplay, or a novel with no interactive\u002Fbranching structure is general writing, not this skill.\n\n## Premise, theme, and pillars (do this first)\n\nNail these before a single branch or line of dialogue. They are the constraint that keeps a branching story from sprawling into incoherence.\n\n1. **Premise** — one sentence: *who*, in *what world*, wants *what*, against *what*. If it doesn't fit in a sentence, the story isn't decided yet.\n2. **Theme** — the question the game argues about (loyalty vs. survival, cost of power). Theme is the filter for every choice; a choice that doesn't press on it is decoration.\n3. **Narrative pillars** — 3–5 non-negotiables the story must always deliver (e.g. \"every companion can die,\" \"the player is never the chosen one\"). Pillars kill scope arguments later.\n4. **Tone & POV** — register (grim, wry, mythic), narrative distance (silent, voiced, ensemble), tense\u002Fperson for text.\n5. **Story-in-service-of-play** — write pillars so they are *expressed through the verbs the player already has*. If the theme is \"trust is earned,\" the game needs a trust mechanic, not a paragraph asserting it.\n\n### Ludonarrative harmony (avoid dissonance)\n\nDissonance is when the story says one thing and the mechanics say the opposite (the \"caring family man\" who murders a thousand henchmen). Diagnose and fix, in order:\n\n- **Verb audit.** List what the player *does* most. Does the dominant verb match the theme and the protagonist's values? If the loop is \"kill,\" a pacifist narrative is dissonant.\n- **Reward audit.** What does the game *reward*? Rewards are the loudest narrative voice — if you reward hoarding but preach generosity, players believe the reward.\n- **Fix by moving the cheaper piece.** Usually re-frame the narrative to match the mechanic rather than re-engineering the mechanic — but flag to **game-design** when only a mechanic change resolves it.\n- **Failure & death.** Reconcile the fiction of losing (respawn, checkpoint, permadeath) with the story; unexplained respawns are the most common silent dissonance.\n\n## Narrative structures for interactivity\n\nPick a topology deliberately; most games mix them. Full trade-offs, diagrams, and containment math → `references\u002Fbranching-and-state.md`.\n\n| Structure | Shape | Player agency | Author cost | Use when |\n| --- | --- | --- | --- | --- |\n| **Linear** | one path, story beats gated by progress | low (pacing only) | low | story-driven, cinematic, tight authorship |\n| **Branching (tree)** | choices split, rarely rejoin | high, expensive | explodes fast | short, choice-showcase, replay-driven |\n| **Hub-and-spoke** | central hub, self-contained spokes, return | medium (order + selection) | moderate, scales | quests\u002Fmissions, RPGs, episodic |\n| **Foldback \u002F string-of-pearls** | branches diverge then **reconverge** at beats | feels high, stays bounded | moderate | the workhorse for long branching stories |\n| **Environmental** | story embedded in space & objects, player-assembled | interpretive | front-loaded | immersive sims, exploration, \"show don't tell\" |\n| **Systemic \u002F emergent** | story generated by rules + player, not scripted | very high, uncurated | design not writing | sims, roguelikes, sandbox; the \"anecdote factory\" |\n\nThe pragmatic default for a story-heavy game is **foldback**: let choices matter locally, then reconverge on load-bearing beats so you author a bounded number of scenes. Pure trees are a trap (see below).\n\n## Branching & choice\n\nA choice is **meaningful** only if the player can (a) form an intent, (b) foresee a plausible consequence, and (c) later *see the consequence land*. Missing any leg makes it noise. Meaningful choice vs. the deliberate, defensible **illusion of choice**, plus state modeling and the combinatorial-explosion fix → `references\u002Fbranching-and-state.md`.\n\n- **Meaningful choice** changes state that the game later reads back to the player (a door, a death, a line, an ending). Track it with a **flag\u002Fvariable**, not a duplicated scene.\n- **Illusion of choice** (options that reconverge to the same outcome) is a legitimate tool for *expression and tone* — but never sell a fake choice as consequential; players feel the betrayal and stop trusting every future choice.\n- **State & flags** are the spine. Model story state as named variables (`met_the_witch`, `reputation >= 3`, `betrayed_ally`). Gate content on state; don't copy-paste branches.\n- **The combinatorial-explosion trap.** N independent binary choices imply 2^N futures — unauthorable past a handful. Contain it with:\n  - **Reconvergence (bottlenecks)** — funnel branches back to shared beats; the space between bottlenecks stays small.\n  - **Gates** — require a flag\u002Flevel\u002Fitem to open content, pruning the live branch set.\n  - **State over structure** — one scene that reads flags and swaps lines beats ten near-duplicate scenes.\n  - **Locality** — most choices affect only the current scene (\"weave\"); reserve the few loud choices for global state.\n\n## Dialogue systems\n\nEvery dialogue tool reduces to the same four primitives — design against these, then let the engine skill wire the chosen tool. Deep tool comparison, a \"pick one\" guide, and the same conversation shown in Ink \u002F Yarn \u002F Twee → `references\u002Fdialogue-tools.md`.\n\n- **Node** — a unit of content (a line, a passage, a knot) with an id you can jump to.\n- **Condition** — boolean over story state that gates a node, option, or line (`if hasKey`, `if trust > 2`).\n- **Variable** — the story state read\u002Fwritten by nodes (flags, counters, enums, inventory).\n- **Effect** — a side effect a node fires (set a flag, give an item, start a quest, emit an engine event).\n\nTools (pointers — do not author engine glue here):\n\n- **Ink** (inkle) — writer-first scripting language: knots\u002Fstitches, diverts `->`, once-only `*` \u002F sticky `+` choices, gathers, weave, `VAR`, `LIST`, tunnels, threads, tags. Great for prose-heavy branching; runs via `inkjs` or engine integrations.\n- **Yarn Spinner** (v3.x, current) — node-based, Twine-friendly: `\u003C\u003Cset $var to x>>`, `\u003C\u003Cif>>`, `\u003C\u003Cjump>>`, commands, functions, markup. First-class Unity; Godot (C# beta, GDScript alpha); Unreal in progress.\n- **Twine** — visual node editor, publishes standalone HTML; scripting depends on the **story format** (Harlowe, SugarCube, Snowman, Chapbook). Twee is its text form — a good neutral interchange.\n- **articy:draft X** — heavyweight visual narrative DB (flow\u002Fdialogue fragments, hubs, conditions, instructions, entities); free Unity\u002FUnreal importers and a **Generic Engine Export** (JSON) for anything else.\n\nAuthor in one of these formats and keep dialogue **portable**; engine binding is a separate step owned by the engine skill.\n\n## Quests & objectives\n\nA quest is a small state machine plus presentation. Spec each quest with:\n\n- **Trigger** — what activates it (talk to X, enter zone, flag set).\n- **Objective(s)** — ordered or parallel steps; each a condition over world\u002Fstory state.\n- **States** — `unavailable → available → active → (step states) → complete \u002F failed`, modeled explicitly. Ambiguous quest state is the #1 quest bug.\n- **Tracking & presentation** — what the player sees (journal, marker, count). Design the *reveal*: don't show a marker for a step the player shouldn't know yet.\n- **Rewards & consequences** — the flags\u002Fitems\u002Fstate the quest writes on completion *and* on failure.\n- **Fail states** — decide per quest: can it fail, and is failure a dead-end, a branch, or lost content? **Failing forward** (failure opens a different path) beats a hard fail; **soft-locking the game** is a defect — always leave an escape.\n- **Nesting & dependencies** — main\u002Fside\u002Fhidden; prerequisite flags; mutual exclusivity (faction A locks B). Track dependencies as gates, per the branching rules above.\n\n## Environmental & systemic storytelling (show, don't tell)\n\nDeliver story *through the world* so the player assembles it and feels ownership. Technique catalog, diegetic-vs-non-diegetic delivery, and the \"anecdote factory\" → `references\u002Fenvironmental-storytelling.md`.\n\n- **Show, don't tell.** Prefer a scene the player reads (a skeleton clutching a locked door) over a paragraph narrating it. Text-dumps are the fallback, not the default.\n- **Environmental storytelling** — set dressing, aftermath\u002Ftraces, spatial sequencing, object placement, and readable item descriptions that imply events without narrating them. Coordinate with **level-design** for the space itself.\n- **Systemic \u002F emergent storytelling** — let rules + player generate stories you didn't script (\"that time my colonist starved defending the fridge\"). You design the *conditions and vocabulary* for stories, not the stories — a **game-design** collaboration.\n- **Diegetic first.** Prefer in-world delivery (signage, barks, world change) over HUD\u002Fnarrator; reserve non-diegetic (menus, codex, narrator) for what the world genuinely can't carry.\n\n## Delivery: pacing, VO, localization-readiness\n\n- **Pace the text.** Match line length to the moment; long paragraphs in combat go unread. Chunk to the display (one box-screen), respect reading speed, never block play with unskippable text.\n- **VO considerations** *(design-side, not recording — that's audio\u002Fengine)* — write for the ear (contractions, short clauses); budget line counts early (VO is expensive and near-frozen once recorded); keep a **stable line ID** on every spoken line; don't splice recorded fragments across variables (gender\u002Fnumber\u002Fname concatenation breaks in most languages).\n- **Localization-readiness** *(so the loc pipeline can do its job)* — externalize all player-facing text to string tables keyed by stable id; **never concatenate** sentences or embed grammar in code (gender\u002Fplural\u002Fword-order differ per language — use full templated strings with ICU-style placeholders); allow +30–40% text expansion; keep variables as named tokens (`{playerName}`), not positional; leave translator notes per line.\n\n## Anti-patterns\n\n| Anti-pattern | Do instead |\n| --- | --- |\n| Branching everything because \"players love choices\" | Pure trees explode (2^N). Use foldback + gates; reconverge on beats. |\n| A choice that feels huge but no later node reads it back | If no later node reads the flag, the choice is noise. Show the consequence or cut it. |\n| Both options lead to the same scene, and it's sold as a big decision | Fine as expression, not as stakes. Never sell a fake choice as consequential. |\n| Explaining in the story why he's a mass murderer | Words don't beat verbs. Fix the ludonarrative dissonance, don't narrate around it. |\n| Adding an audio log to explain the backstory | Text-dump is the fallback. Try to *show* it environmentally first. |\n| Hardcoding strings, \"we'll localize later\" | Concatenation and hardcoded text break loc. Externalize to keyed string tables now. |\n| A quest that can't be failed because it's simpler that way | Sometimes right; but soft-locking the game on a missed step is a defect — leave an escape. |\n| Wiring the Ink file into Unity here | Not this skill. Author portable narrative; hand wiring to the engine skill. |\n\n## Checklist\n\n- [ ] Premise (one sentence), theme, and 3–5 narrative pillars are written and agreed; every pillar is expressible through an existing player verb (no assert-only themes).\n- [ ] Verb + reward audit done; any ludonarrative dissonance is fixed or escalated to game-design.\n- [ ] A topology is chosen deliberately (default: foldback), not accidental tree sprawl; combinatorial explosion is contained (reconvergence + gates + locality) so the branch count is authorable.\n- [ ] Story state is modeled as named variables\u002Fflags; content gates on state, not duplicated scenes.\n- [ ] Every \"meaningful\" choice writes a flag some later node reads back to the player; no fake choice is sold as consequential.\n- [ ] Dialogue authored in a portable format (Ink\u002FYarn\u002FTwee\u002Farticy); engine wiring left to the engine skill.\n- [ ] Each quest has explicit states, tracking, rewards\u002Fconsequences, and a defined fail behavior (no silent soft-locks).\n- [ ] Environmental\u002Fdiegetic delivery preferred over text-dumps and non-diegetic narration where the world can carry it.\n- [ ] All player-facing text externalized to keyed string tables; no concatenation; variables are named tokens; +30–40% expansion allowed.\n- [ ] VO lines have stable IDs, are written for the ear, and the script is locked before recording is proposed.\n","# Game Storytelling — Narrative Design (engine-agnostic)\n\n*Design the story as a system the player operates, not a script they watch. This skill owns the narrative graph — premise, pillars, branches, choices, dialogue state, quests, and the storytelling embedded in the world.*\n\nYou produce **design artifacts**: a premise\u002Ftheme\u002Fpillars doc, a branch topology, a state\u002Fflag table, dialogue in a portable format (Ink\u002FYarn\u002FTwee\u002Farticy), quest specs, and environmental beats. Story is a **system in service of play**; when you catch yourself designing a great scene the mechanics can't honor, reconcile it (see Ludonarrative harmony) rather than ship the dissonance.\n\nBoundaries: **game-design** owns what the player *does* — core loop, verbs, systems, progression, economy, difficulty, balance — and the story serves those verbs; call it when resolving dissonance needs a *mechanic* change, or when designing the conditions for systemic\u002Femergent story. **level-design** owns spatial layout, encounter placement, sightlines, blockout and the pacing *of a space* — the space environmental storytelling lives inside; co-own the set-dressing. **godot \u002F unity \u002F unreal** implement the dialogue runner, quest state, save-serialization of story state, and the Ink\u002FYarn\u002Farticy plugin glue — author portable, they wire it. **marketing** owns the store page, premise pitch and trailer copy (external-facing, not in-game narrative). Prose fiction, a screenplay, or a novel with no interactive\u002Fbranching structure is general writing, not this skill.\n\n## Premise, theme, and pillars (do this first)\n\nNail these before a single branch or line of dialogue. They are the constraint that keeps a branching story from sprawling into incoherence.\n\n1. **Premise** — one sentence: *who*, in *what world*, wants *what*, against *what*. If it doesn't fit in a sentence, the story isn't decided yet.\n2. **Theme** — the question the game argues about (loyalty vs. survival, cost of power). Theme is the filter for every choice; a choice that doesn't press on it is decoration.\n3. **Narrative pillars** — 3–5 non-negotiables the story must always deliver (e.g. \"every companion can die,\" \"the player is never the chosen one\"). Pillars kill scope arguments later.\n4. **Tone & POV** — register (grim, wry, mythic), narrative distance (silent, voiced, ensemble), tense\u002Fperson for text.\n5. **Story-in-service-of-play** — write pillars so they are *expressed through the verbs the player already has*. If the theme is \"trust is earned,\" the game needs a trust mechanic, not a paragraph asserting it.\n\n### Ludonarrative harmony (avoid dissonance)\n\nDissonance is when the story says one thing and the mechanics say the opposite (the \"caring family man\" who murders a thousand henchmen). Diagnose and fix, in order:\n\n- **Verb audit.** List what the player *does* most. Does the dominant verb match the theme and the protagonist's values? If the loop is \"kill,\" a pacifist narrative is dissonant.\n- **Reward audit.** What does the game *reward*? Rewards are the loudest narrative voice — if you reward hoarding but preach generosity, players believe the reward.\n- **Fix by moving the cheaper piece.** Usually re-frame the narrative to match the mechanic rather than re-engineering the mechanic — but flag to **game-design** when only a mechanic change resolves it.\n- **Failure & death.** Reconcile the fiction of losing (respawn, checkpoint, permadeath) with the story; unexplained respawns are the most common silent dissonance.\n\n## Narrative structures for interactivity\n\nPick a topology deliberately; most games mix them. Full trade-offs, diagrams, and containment math → `references\u002Fbranching-and-state.md`.\n\n| Structure | Shape | Player agency | Author cost | Use when |\n| --- | --- | --- | --- | --- |\n| **Linear** | one path, story beats gated by progress | low (pacing only) | low | story-driven, cinematic, tight authorship |\n| **Branching (tree)** | choices split, rarely rejoin | high, expensive | explodes fast | short, choice-showcase, replay-driven |\n| **Hub-and-spoke** | central hub, self-contained spokes, return | medium (order + selection) | moderate, scales | quests\u002Fmissions, RPGs, episodic |\n| **Foldback \u002F string-of-pearls** | branches diverge then **reconverge** at beats | feels high, stays bounded | moderate | the workhorse for long branching stories |\n| **Environmental** | story embedded in space & objects, player-assembled | interpretive | front-loaded | immersive sims, exploration, \"show don't tell\" |\n| **Systemic \u002F emergent** | story generated by rules + player, not scripted | very high, uncurated | design not writing | sims, roguelikes, sandbox; the \"anecdote factory\" |\n\nThe pragmatic default for a story-heavy game is **foldback**: let choices matter locally, then reconverge on load-bearing beats so you author a bounded number of scenes. Pure trees are a trap (see below).\n\n## Branching & choice\n\nA choice is **meaningful** only if the player can (a) form an intent, (b) foresee a plausible consequence, and (c) later *see the consequence land*. Missing any leg makes it noise. Meaningful choice vs. the deliberate, defensible **illusion of choice**, plus state modeling and the combinatorial-explosion fix → `references\u002Fbranching-and-state.md`.\n\n- **Meaningful choice** changes state that the game later reads back to the player (a door, a death, a line, an ending). Track it with a **flag\u002Fvariable**, not a duplicated scene.\n- **Illusion of choice** (options that reconverge to the same outcome) is a legitimate tool for *expression and tone* — but never sell a fake choice as consequential; players feel the betrayal and stop trusting every future choice.\n- **State & flags** are the spine. Model story state as named variables (`met_the_witch`, `reputation >= 3`, `betrayed_ally`). Gate content on state; don't copy-paste branches.\n- **The combinatorial-explosion trap.** N independent binary choices imply 2^N futures — unauthorable past a handful. Contain it with:\n  - **Reconvergence (bottlenecks)** — funnel branches back to shared beats; the space between bottlenecks stays small.\n  - **Gates** — require a flag\u002Flevel\u002Fitem to open content, pruning the live branch set.\n  - **State over structure** — one scene that reads flags and swaps lines beats ten near-duplicate scenes.\n  - **Locality** — most choices affect only the current scene (\"weave\"); reserve the few loud choices for global state.\n\n## Dialogue systems\n\nEvery dialogue tool reduces to the same four primitives — design against these, then let the engine skill wire the chosen tool. Deep tool comparison, a \"pick one\" guide, and the same conversation shown in Ink \u002F Yarn \u002F Twee → `references\u002Fdialogue-tools.md`.\n\n- **Node** — a unit of content (a line, a passage, a knot) with an id you can jump to.\n- **Condition** — boolean over story state that gates a node, option, or line (`if hasKey`, `if trust > 2`).\n- **Variable** — the story state read\u002Fwritten by nodes (flags, counters, enums, inventory).\n- **Effect** — a side effect a node fires (set a flag, give an item, start a quest, emit an engine event).\n\nTools (pointers — do not author engine glue here):\n\n- **Ink** (inkle) — writer-first scripting language: knots\u002Fstitches, diverts `->`, once-only `*` \u002F sticky `+` choices, gathers, weave, `VAR`, `LIST`, tunnels, threads, tags. Great for prose-heavy branching; runs via `inkjs` or engine integrations.\n- **Yarn Spinner** (v3.x, current) — node-based, Twine-friendly: `\u003C\u003Cset $var to x>>`, `\u003C\u003Cif>>`, `\u003C\u003Cjump>>`, commands, functions, markup. First-class Unity; Godot (C# beta, GDScript alpha); Unreal in progress.\n- **Twine** — visual node editor, publishes standalone HTML; scripting depends on the **story format** (Harlowe, SugarCube, Snowman, Chapbook). Twee is its text form — a good neutral interchange.\n- **articy:draft X** — heavyweight visual narrative DB (flow\u002Fdialogue fragments, hubs, conditions, instructions, entities); free Unity\u002FUnreal importers and a **Generic Engine Export** (JSON) for anything else.\n\nAuthor in one of these formats and keep dialogue **portable**; engine binding is a separate step owned by the engine skill.\n\n## Quests & objectives\n\nA quest is a small state machine plus presentation. Spec each quest with:\n\n- **Trigger** — what activates it (talk to X, enter zone, flag set).\n- **Objective(s)** — ordered or parallel steps; each a condition over world\u002Fstory state.\n- **States** — `unavailable → available → active → (step states) → complete \u002F failed`, modeled explicitly. Ambiguous quest state is the #1 quest bug.\n- **Tracking & presentation** — what the player sees (journal, marker, count). Design the *reveal*: don't show a marker for a step the player shouldn't know yet.\n- **Rewards & consequences** — the flags\u002Fitems\u002Fstate the quest writes on completion *and* on failure.\n- **Fail states** — decide per quest: can it fail, and is failure a dead-end, a branch, or lost content? **Failing forward** (failure opens a different path) beats a hard fail; **soft-locking the game** is a defect — always leave an escape.\n- **Nesting & dependencies** — main\u002Fside\u002Fhidden; prerequisite flags; mutual exclusivity (faction A locks B). Track dependencies as gates, per the branching rules above.\n\n## Environmental & systemic storytelling (show, don't tell)\n\nDeliver story *through the world* so the player assembles it and feels ownership. Technique catalog, diegetic-vs-non-diegetic delivery, and the \"anecdote factory\" → `references\u002Fenvironmental-storytelling.md`.\n\n- **Show, don't tell.** Prefer a scene the player reads (a skeleton clutching a locked door) over a paragraph narrating it. Text-dumps are the fallback, not the default.\n- **Environmental storytelling** — set dressing, aftermath\u002Ftraces, spatial sequencing, object placement, and readable item descriptions that imply events without narrating them. Coordinate with **level-design** for the space itself.\n- **Systemic \u002F emergent storytelling** — let rules + player generate stories you didn't script (\"that time my colonist starved defending the fridge\"). You design the *conditions and vocabulary* for stories, not the stories — a **game-design** collaboration.\n- **Diegetic first.** Prefer in-world delivery (signage, barks, world change) over HUD\u002Fnarrator; reserve non-diegetic (menus, codex, narrator) for what the world genuinely can't carry.\n\n## Delivery: pacing, VO, localization-readiness\n\n- **Pace the text.** Match line length to the moment; long paragraphs in combat go unread. Chunk to the display (one box-screen), respect reading speed, never block play with unskippable text.\n- **VO considerations** *(design-side, not recording — that's audio\u002Fengine)* — write for the ear (contractions, short clauses); budget line counts early (VO is expensive and near-frozen once recorded); keep a **stable line ID** on every spoken line; don't splice recorded fragments across variables (gender\u002Fnumber\u002Fname concatenation breaks in most languages).\n- **Localization-readiness** *(so the loc pipeline can do its job)* — externalize all player-facing text to string tables keyed by stable id; **never concatenate** sentences or embed grammar in code (gender\u002Fplural\u002Fword-order differ per language — use full templated strings with ICU-style placeholders); allow +30–40% text expansion; keep variables as named tokens (`{playerName}`), not positional; leave translator notes per line.\n\n## Anti-patterns\n\n| Anti-pattern | Do instead |\n| --- | --- |\n| Branching everything because \"players love choices\" | Pure trees explode (2^N). Use foldback + gates; reconverge on beats. |\n| A choice that feels huge but no later node reads it back | If no later node reads the flag, the choice is noise. Show the consequence or cut it. |\n| Both options lead to the same scene, and it's sold as a big decision | Fine as expression, not as stakes. Never sell a fake choice as consequential. |\n| Explaining in the story why he's a mass murderer | Words don't beat verbs. Fix the ludonarrative dissonance, don't narrate around it. |\n| Adding an audio log to explain the backstory | Text-dump is the fallback. Try to *show* it environmentally first. |\n| Hardcoding strings, \"we'll localize later\" | Concatenation and hardcoded text break loc. Externalize to keyed string tables now. |\n| A quest that can't be failed because it's simpler that way | Sometimes right; but soft-locking the game on a missed step is a defect — leave an escape. |\n| Wiring the Ink file into Unity here | Not this skill. Author portable narrative; hand wiring to the engine skill. |\n\n## Checklist\n\n- [ ] Premise (one sentence), theme, and 3–5 narrative pillars are written and agreed; every pillar is expressible through an existing player verb (no assert-only themes).\n- [ ] Verb + reward audit done; any ludonarrative dissonance is fixed or escalated to game-design.\n- [ ] A topology is chosen deliberately (default: foldback), not accidental tree sprawl; combinatorial explosion is contained (reconvergence + gates + locality) so the branch count is authorable.\n- [ ] Story state is modeled as named variables\u002Fflags; content gates on state, not duplicated scenes.\n- [ ] Every \"meaningful\" choice writes a flag some later node reads back to the player; no fake choice is sold as consequential.\n- [ ] Dialogue authored in a portable format (Ink\u002FYarn\u002FTwee\u002Farticy); engine wiring left to the engine skill.\n- [ ] Each quest has explicit states, tracking, rewards\u002Fconsequences, and a defined fail behavior (no silent soft-locks).\n- [ ] Environmental\u002Fdiegetic delivery preferred over text-dumps and non-diegetic narration where the world can carry it.\n- [ ] All player-facing text externalized to keyed string tables; no concatenation; variables are named tokens; +30–40% expansion allowed.\n- [ ] VO lines have stable IDs, are written for the ear, and the script is locked before recording is proposed.\n",{"name":5,"tags":24,"origin":32,"profiles":33,"recommends":35,"description":7},[25,26,27,28,29,30,31],"game","narrative","story","dialogue","quest","branching","worldbuilding","risco",[34],"full",[36,37],"game-design","level-design","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fgame-storytelling",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill game-storytelling",{"tool":52,"command":53},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill game-storytelling",{"tool":55,"command":56},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill game-storytelling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002FSKILL.md",true,[60,66,70,74,78],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"evals\u002Fcases.yaml","REFERENCE","参考文档",6015,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002Fevals\u002Fcases.yaml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"evals\u002FREADME.md",1603,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002Fevals\u002FREADME.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fbranching-and-state.md",7969,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002Freferences\u002Fbranching-and-state.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fdialogue-tools.md",7286,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002Freferences\u002Fdialogue-tools.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fenvironmental-storytelling.md",7375,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fgame-storytelling\u002Freferences\u002Fenvironmental-storytelling.md",[83,91,96,103,110,117],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":92,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":90},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":90},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":90},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":90},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":90},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]