book-game
starsforks
How to install book-game?
epicsagas/velith/book-game
$npx -y skills add epicsagas/Velith --skill book-gameGame scenario patterns — quest/event trees, branching dialogue, world-building, character arcs across routes, lore bibles.
SKILL.md
| 1 | # Game Scenario Patterns |
| 2 | |
| 3 | **Story architecture**: Main scenario (critical path, 60%) + Side scenarios (optional, 30%) + Hidden scenarios (easter eggs, 10%). Critical path must work standalone; side scenarios enrich but never gate main progression. |
| 4 | |
| 5 | **Branching structure**: Binary choice (A/B), multi-way (3+ options), conditional (requires item/flag), timed (deadline-based). Branch depth: ≤4 levels before convergence. Convergence types: full (all paths merge), partial (some carry forward), butterfly (small choice → big consequence later). |
| 6 | |
| 7 | **Quest design**: Objective (clear goal) → Prerequisites (what player needs) → Steps (3-7 per quest, each with verification) → Branch points (player agency) → Resolution + Reward. Quest chains: linear (A→B→C), hub (return to base between quests), parallel (simultaneous tracks). |
| 8 | |
| 9 | **Dialogue system**: Dialogue nodes with speaker, line, emotion tag, and next-node links. Player responses: investigate (info), persuade (relationship), action (consequence). Branch dialogue: ≤3 choices per node. Emotional tone tracking per NPC (friendly/neutral/hostile affects available options). |
| 10 | |
| 11 | **World-building layers**: Geography (maps, regions, travel routes) → History (timeline, key events, ruins) → Culture (factions, beliefs, customs, taboos) → Economy (resources, trade, scarcity) → Ecology (creatures, environments, hazards). Each layer must be consistent and interconnected. |
| 12 | |
| 13 | **Character arc across routes**: Core identity (consistent across all routes) + Route-specific development. NPC relationship system: trust level (0-100) with threshold gates. Companion characters: personal quest triggered by trust threshold. |
| 14 | |
| 15 | **Lore bible**: Entry per: location, character, faction, item, event, concept. Fields: name, description, connections (linked entries), game-mechanic relevance, narrative role. Consistency check: cross-reference all entries before finalizing. |
| 16 | |
| 17 | **Scenario document structure**: Overview (concept, tone, themes) → World bible → Character bible → Main quest line → Side quests → Dialogue trees → Cutscene scripts → Branching map (visual flowchart). Each quest has: ID, title, summary, prerequisites, steps, branches, rewards, flags set. |
| 18 | |
| 19 | **Format**: Markdown with YAML frontmatter per quest/node. Branching maps as Mermaid flowcharts. Dialogue as structured blocks with speaker/emotion/response fields. |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
