rpg

1# RPG
2 
3A playbook for role-playing games — stats and progression, inventory/equipment, quests,
4dialogue, and combat. This is a **compositional** skill: it ties data-driven content,
5dialogue, and saving together. It does not re-teach those primitives; it defines the systems
6that make growth and choice feel meaningful, and points to the skills that implement each.
7 
8These systems also apply to custom/proprietary engines. Keep the project's engine and bind
9the concepts below to its documented data, events, UI, and save interfaces. Inspect local
10source/SDK examples before choosing APIs; the router's custom-engine fallback guides that
11mapping. Godot/Unity bindings below are examples, not prerequisites.
12 
13## When to use
14 
15- Use when building an RPG/JRPG/action-RPG: the player has **stats that grow**, an
16  **inventory**, **quests**, **dialogue**, and persistent progress.
17- Use when designing a leveling curve, a damage formula, an inventory/equipment model, or a
18  quest state machine.
19 
20**When *not* to use:** permadeath dungeon runs with no persistent character → `roguelike`.
21Pure conversation/branching story → `visual-novel`. Open-world needs/crafting/base-building →
22`survival-crafting`. For the dialogue engine itself, use `dialogue-systems`.
23 
24## Core loop
25 
26**Explore → encounter (fight / talk / solve) → earn rewards (XP, loot, story) → grow
27(level up, gear up, unlock) → take on harder content.** The fantasy is *getting stronger and
28…