init
This commit is contained in:
commit
971e49db5c
246 changed files with 93082 additions and 0 deletions
37
.claude/skills/session-recap/SKILL.md
Normal file
37
.claude/skills/session-recap/SKILL.md
Normal file
|
|
@ -0,0 +1,37 @@
|
|||
---
|
||||
name: session-recap
|
||||
description: Turn rough session notes (or a transcript/bullet list the DM pastes) into a polished narrative Session Recap in the Baltun'ia house style, correctly numbered and dated, then update or stub the entity notes (NPCs, POIs, factions) that appeared. Use after a game session, or when the DM says "write up the recap", "log last night's session", "recap what happened".
|
||||
---
|
||||
|
||||
# Write a Session Recap
|
||||
|
||||
First read `.claude/skills/_shared/vault-conventions.md` and **two existing
|
||||
recaps** (e.g. `3. Session Recaps/1. Opening - 7-21-25.md` and `6. Taylor's Manor - 9-22-25.md`)
|
||||
to match the prose style: flowing third-person past tense, present the events as
|
||||
a story, italicize spoken names/quotes (`_Hofta Baldwin_`), no bullet lists.
|
||||
|
||||
## Steps
|
||||
|
||||
1. **Get the inputs.** Take the DM's raw notes. Ask for the **session date** and
|
||||
a **short title** if not given. Determine the next recap number by listing
|
||||
`3. Session Recaps/` and adding 1 to the highest `N`.
|
||||
|
||||
2. **Ground it.** Read the previous recap and `z_other/Campaign Flow.md` so the
|
||||
opening picks up exactly where the party left off and names match canon.
|
||||
|
||||
3. **Draft the narrative.** Convert notes into the house style — coherent prose,
|
||||
correct in-world names, the party's actual choices, consequences, and any
|
||||
cliffhanger. Keep it faithful to the notes; flag anything ambiguous rather
|
||||
than inventing plot.
|
||||
|
||||
4. **Confirm before saving.** Show the draft. This is a record of what *actually
|
||||
happened* — let the DM correct facts before it becomes canon.
|
||||
|
||||
5. **Save** as `3. Session Recaps/<N>. <Title> - <M-D-YY>.md` (no leading zeros
|
||||
in the date).
|
||||
|
||||
6. **Propagate to the world.** List every entity that appeared. For each:
|
||||
- existing note → append the new development (e.g. an NPC's death, a new
|
||||
alliance) to the right section;
|
||||
- new entity → offer to create it via create-npc / create-poi / create-faction.
|
||||
Update Campaign Flow if a major branch resolved. Keep wikilinks consistent.
|
||||
Loading…
Add table
Add a link
Reference in a new issue