narrative-character-design-narrative
Use when creating game characters, NPCs, character arcs, dialogue systems, archetypes, or character bibles. Triggers: character, NPC, dialogue, archetype, character bible, motivation arc.
Best use case
narrative-character-design-narrative is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when creating game characters, NPCs, character arcs, dialogue systems, archetypes, or character bibles. Triggers: character, NPC, dialogue, archetype, character bible, motivation arc.
Teams using narrative-character-design-narrative should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/character-design-narrative/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How narrative-character-design-narrative Compares
| Feature / Agent | narrative-character-design-narrative | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when creating game characters, NPCs, character arcs, dialogue systems, archetypes, or character bibles. Triggers: character, NPC, dialogue, archetype, character bible, motivation arc.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Character Design (Narrative) ## Purpose Character archetypes, motivation arcs, dialogue systems, and character bibles for game characters. Genre-agnostic — applies to any game with characters, NPCs, or player-created identities. ## When to Use Trigger: character design, NPC design, character arc, dialogue system, character bible, character motivation, archetype, companion, antagonist, player character, voice, personality, character writing ## Prerequisites - `worldbuilding` — characters must fit the world - `quest-narrative-coherence` — character actions must be consistent with established lore ## Core Principles > Hideo Kojima: "Characters should feel like they exist beyond the player's experience of them." > Hidetaka Miyazaki: "Every character has a history. The player sees only the tip of the iceberg." > Jenova Chen: "Characters don't need words to communicate. Presence and movement tell the story." 1. **Characters want things** — every character (NPC or player) must have a clear motivation that drives their actions 2. **Consistency over surprise** — a character acting out of established personality must be justified by narrative events 3. **Characters exist beyond the player** — NPCs should have lives, routines, and goals independent of the player's actions 4. **Show personality through action** — what a character DOES reveals more than what they SAY 5. **Flaws make characters interesting** — perfect characters are forgettable; memorable characters have contradictions 6. **Archetypes as starting points** — use archetypes for structure, then subvert or deepen them 7. **Voice consistency** — each character should have a distinct way of speaking that a player could identify without names ## Character Archetype Toolkit | Archetype | Core Trait | Typical Role | Subversion Example | |-----------|-----------|-------------|-------------------| | Mentor | Wisdom | Guide player early | Mentor has hidden agenda | | Trickster | Deception | Comic relief / chaos | Trickster is the most honest character | | Guardian | Protection | Block progress until ready | Guardian is protecting something terrible | | Herald | Information | Deliver news / quests | Herald's news is always wrong | | Shadow | Opposition | Antagonist / dark mirror | Shadow is justified in their actions | | Ally | Support | Help in challenges | Ally has their own quest that conflicts | | Shapeshifter | Ambiguity | Uncertain loyalty | Shapeshifter is the only constant | ## Character Bible Structure For each significant character, document: 1. **Identity**: Name, age, appearance, role, faction 2. **Motivation**: What they want (public) and what they need (hidden) 3. **History**: Backstory that explains their current state 4. **Personality**: 3-5 defining traits, speech patterns, quirks 5. **Relationships**: Connections to other characters 6. **Arc**: How they change over the story (or why they don't) 7. **Gameplay role**: What they do mechanically (quest giver, shop, companion, boss) ## Cross-References - `worldbuilding` — characters exist within the world's rules - `quest-narrative-coherence` — character consistency validation - `story-structure-game` — character arcs within narrative structure - `quest-mission-design` — characters as quest givers and participants - `elevenlabs-sound-music` — voice acting for characters ## Pitfalls & Anti-Patterns - **"Walking exposition"** — NPC exists only to deliver information - **"Personality-free quest giver"** — NPC with no personality, just a quest marker - **"Sudden betrayal"** — character betrays without foreshadowing; feels cheap - **"One-note villain"** — antagonist with no understandable motivation - **"Static cast"** — no character changes or grows throughout the game - **"Everyone talks the same"** — all NPCs have identical voice/personality ## Designer Philosophy **Hideo Kojima** (Metal Gear Solid): Characters are more than their function. The Boss, Ocelot, and Otacon all exist as complete people with histories, philosophies, and motivations. Even minor characters have enough depth that players wonder about their lives off-screen. **Hidetaka Miyazaki** (Dark Souls, Elden Ring): The most compelling characters are the ones you piece together. Solaire's sunny optimism in a dying world, Siegmeyer's fading courage — their stories unfold through brief encounters and item descriptions, creating a bond stronger than any cutscene. **Jenova Chen** (Journey): Sometimes the most powerful character is another player. Journey's companions communicate without words, creating genuine emotional connection through shared experience. Characters don't always need dialogue to be memorable. ## Sources - "Creating Compelling Game Characters" — GDC 2016 - "Writing Diverse Characters" — GDC 2019 - "The Writer's Journey" — Christopher Vogler (adapted for games) - "Character Design for Games" — GDC 2018
Related Skills
narrative-worldbuilding
Use when creating game worlds, lore, factions, geography, timelines, or establishing world consistency rules. Genre-agnostic — works for fantasy, sci-fi, modern, or abstract settings. Triggers: lore, factions, geography, world bible, world creation.
narrative-story-structure-game
Use when designing interactive narratives, branching storylines, player agency systems, non-linear story structures, or act frameworks for games. Triggers: branching narrative, player agency, story arc, interactive story, dialogue.
narrative-quest-narrative-coherence
Use when creating any quest, mission, or story content — enforces the 5-step narrative coherence check: lore validation, conflict detection, quest registry, and contradiction prevention. Triggers: coherence check, lore validation, quest registry, narrative consistency.
design-ui-ux-game
Use when designing game UI — HUD patterns, menu systems, onboarding flows, feedback loops, accessibility features, or notification systems. Triggers: HUD, menu, onboarding, accessibility, UI, UX, game interface.
design-skill-progression-trees
Use when designing or implementing skill trees, talent trees, ability progression systems, or unlock graphs. Triggers: skill tree, talent tree, ability tree, progression system, unlock, prestige, node, skill points.
design-quest-mission-design
Use when designing quests, missions, objectives, quest trees, or reward structures. Requires quest-narrative-coherence check before any quest creation. Triggers: quest, mission, objectives, quest tree, rewards.
design-procedural-gen
Use when implementing procedural content generation, dungeon or map generation, procedural loot tables, world seeds, noise-based terrain, NPC behavior variation, or wave function collapse. Triggers: procedural, dungeon gen, map gen, loot table, world seed, noise, BSP, wave function collapse, randomization.
design-level-design
Use when designing game levels, environments, difficulty curves, pacing, encounter placement, or spatial layouts for any game genre. Triggers: level, pacing, difficulty curve, encounter, environment, spatial design.
design-game-economy-design
Use when designing virtual economies, currencies, sink/faucet balance, loot tables, crafting systems, shops, or inflation control. Triggers: economy, currency, sinks, loot, inflation, crafting, shop.
design-game-design-fundamentals
Use when designing core game loops, feedback systems, player motivation models, MDA framework analysis, progression curves, difficulty tuning, reward schedules, or any genre-agnostic game design theory.
react-animations
Use when implementing animations, transitions, or motion effects in React apps. Invoke this skill whenever someone asks about animation, transition, motion, framer motion, react spring, GSAP, entrance/exit effects, scroll animation, parallax, gesture, drag, card flip, screen shake, health bar, damage numbers, loading states, page transitions, hover effects, or any element that should move, fade, scale, or respond to interaction — even if they don't use the word "animation".
openclaw-genie
Use when the user asks about OpenClaw — installation, configuration, agents, channels, memory, tools, hooks, skills, deployment, Docker, multi-agent, OAuth, gateway, CLI, browser, exec, PDF, voice, secrets, sandboxing, sessions, cron, webhooks, heartbeat, sub-agents, nodes, companion devices, canvas, camera, or messaging platform integration. Also invoke for questions about running OpenClaw agents: memory recall (memory_search), cron scheduling, multi-agent setup, or any openclaw.json behavior. OpenClaw has proprietary configuration syntax (SecretRef, dmPolicy, node.invoke, tool profiles) and CLI commands that require this skill to answer correctly.