Narrative Designer

Design branching dialogue and lore systems with gameplay consequences for RPGs.

110|18|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill narrative-designer-travisleeeeee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Narrative Designer
Source: https://github.com/TravisLeeeeee/awesome-openclaw-personas/tree/main/personas/game-development/narrative-designer
Command: npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill narrative-designer-travisleeeeee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of writing game narrative that feels disconnected from gameplay by giving you a repeatable framework for branching dialogue, lore architecture, and environmental storytelling that produce observable consequences.

Core Features & Use Cases

  • Dialogue that reads like humans: Enforces character voice pillars and “no exposition disguised as conversation” standards for believable, playable interactions.
  • Meaningful branching with convergence: Designs decision trees where branches differ in kind, converge cleanly, and deliver consequences within a short window.
  • Lore designed for comprehension and discovery: Builds a three-tier lore structure (Surface/Engaged/Deep) backed by a world bible so optional content never contradicts the core story.
  • Narrative-to-gameplay integration: Ensures every major story beat maps to gameplay consequences (mechanics, access, world state, rewards) so players feel the world responding to choices.

Quick Start

Use the Narrative Designer skill to produce an engine-ready branching dialogue prototype (Ink/Yarn/Twine) for a first-meeting scene that includes voice-consistent lines, a consequence tree, and environmental storytelling beats for the same level.

Frequently Asked Questions about Narrative Designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design branching dialogue that feels connected to gameplay?

Design branching dialogue by mapping decision trees to observable gameplay consequences like mechanics, access, world state, and rewards. This ensures narrative choices produce meaningful differences and converge cleanly, preventing story and gameplay disconnect.

What is the best way to structure game lore for optional discovery without contradictions?

Structure game lore using a three-tier architecture—Surface, Engaged, and Deep—backed by a world bible. This maintains consistency across optional content and core story, ensuring deep lore never contradicts the main narrative.

How do I write RPG dialogue that avoids exposition disguised as conversation?

Write RPG dialogue by enforcing strict character voice pillars that prioritize believable, playable interactions. This framework eliminates forced exposition, ensuring characters speak naturally within the story-driven game environment.

Can I generate engine-ready dialogue prototypes using Ink or Yarn Spinner?

You can generate engine-ready branching dialogue prototypes for Ink, Yarn Spinner, or Twine. The output includes voice-consistent lines, consequence trees, and environmental storytelling beats formatted directly for game engine implementation.

Does narrative design for story-driven games require a full world bible?

Narrative design for story-driven games requires a world bible to maintain three-tier lore consistency. It ensures that branching choices, character voices, and environmental storytelling align with the established core story constraints.

How to ensure player agency in branching narrative convergence?

Ensure player agency in branching narrative convergence by designing decision trees where branches differ in kind and deliver consequences within a short window. Testing confirms players feel the world responding to their specific choices.