69 KiB
name, description
| name | description |
|---|---|
| adult-visual-novel-narrative | Guides the creation of narrative content for adult visual novels — story structure, character design, worldbuilding, branching plotlines, erotic scene writing, dialogue craft, and pacing. Completely tech-independent; applies to any engine, tool, or format. |
Adult Visual Novel Narrative Skill
A craft-focused guide for writing narrative content in adult visual novels. This skill covers story architecture, character design, worldbuilding, branching plots, erotic writing, dialogue, and pacing — all independent of any specific engine or tool.
0. Artifacts — Living Narrative Documents
This skill produces and maintains a set of markdown files inside docs/narrative/ that track the narrative's current state. Think of them as a living bible — they evolve as the story is written, revised, and expanded. Whenever narrative content is created or changed, update the relevant artifacts to reflect the new state.
Artifact Overview
| File | Status | Purpose |
|---|---|---|
docs/narrative/STORY.md |
Mandatory | Master story document: logline, structure, chapter outline, current progress, scene status |
docs/narrative/CHARACTER_DESIGN.md |
Mandatory | Character profiles: archetype, voice, arc, intimacy style, relationships |
docs/narrative/WORLD_BUILDING.md |
Mandatory | Setting, geography, atmosphere, rules, sensory motifs, locations |
docs/narrative/ROUTES_AND_CHOICES.md |
Mandatory | Route structure, affinity system, choice catalog, branching map |
docs/narrative/EROTIC_CONTENT.md |
Optional | Five-stage intimacy model tracking per route, consent framing, scene staging |
When to Create / Update
- New project: Create all mandatory files with initial outlines before writing any scene.
- New chapter / scene: Update
STORY.md(scene status, progress) andROUTES_AND_CHOICES.md(choices, affinity changes). - New character: Update
CHARACTER_DESIGN.mdwith full profile. - New location: Update
WORLD_BUILDING.mdwith geography, atmosphere, and sensory tags. - Erotic scene written: Update
EROTIC_CONTENT.mdwith stage progression and notes. - Plot revision: Update affected artifacts to reflect the new state. Remove outdated information.
How to Update
- Append new information under the relevant section heading.
- Mark completed scenes with
[x]in checklists. - Outdated entries should be struck through (
~~like this~~) or removed, with a note in the Change Log section. - Every update adds a line to the Change Log at the bottom of the file:
YYYY-MM-DD — What changed and why.
STORY.md — Master Story Document
Path: docs/narrative/STORY.md
Mandatory: Yes
Captures the entire story architecture in one place. Every scene, every chapter, every major beat lives here.
# STORY.md — [Project Title]
> **Logline:** A one-sentence summary of the entire story.
> **Tone:** [Warm / Melancholic / Playful / Intense / etc.]
> **Content Rating:** [All-ages / 16+ / 18+ / Explicit]
> **Estimated Playtime:** [Short (<5h) / Medium (5-15h) / Long (15h+)]
> **Route Count:** [Number of romanceable characters with full routes]
---
### Three-Act Structure
#### Act I — Setup (~25%)
> **What happens:** Brief summary of the act's purpose.
> **Ends with:** The point of no return — what commits the protagonist to this journey.
| Chapter | Title | Summary | Status |
|---------|-------|---------|--------|
| 1 | [Chapter 1 Title] | What happens in this chapter. Who the protagonist meets. First choices. | [ ] / [x] |
| 2 | [Chapter 2 Title] | Continuing setup. Second major character introduction. | [ ] / [x] |
#### Act II — Branching (~50%)
> **What happens:** Routes diverge. Each route explores a different character's arc.
> **Midpoint:** The revelation or crisis that deepens the central relationship.
> **Ends with:** Route lock-in — the player is committed to one character.
| Chapter | Title | Summary | Affects | Status |
|---------|-------|---------|---------|--------|
| 3 | [Chapter 3 Title] | [Summary] | [CharacterA route] | [ ] / [x] |
| 4 | [Chapter 4 Title] | [Summary] | [CharacterB route] | [ ] / [x] |
#### Act III — Resolution (~25%)
> **What happens:** Consequences of the climax play out. Emotional resolution per route.
> **Endings:** List each route's ending type (happy, bittersweet, tragic, open).
| Chapter | Title | Summary | Route | Status |
|---------|-------|---------|-------|--------|
| 7 | [Chapter 7 Title] | [Summary] | [CharacterA] | [ ] / [x] |
| 8 | [Chapter 8 Title] | [Summary] | [CharacterB] | [ ] / [x] |
---
### Scene-by-Scene Outline
#### Chapter 1: [Title]
**Emotional arc:** [Where the chapter starts → where it ends emotionally]
**Central question:** [What this chapter asks the player]
##### Scene 1 — [Scene Title]
| Field | Value |
|-------|-------|
| **Location** | Where it takes place |
| **Time** | Time of day, season |
| **Characters** | Who is present |
| **Tone** | Emotional register of this scene |
| **Choices** | Number of player choices in this scene |
| **Content** | SFW / Suggestive / Explicit |
| **Status** | [ ] Outline / [x] Written / [x] Revised |
**What happens:**
A short paragraph describing the scene's action.
**Key moments:**
- Beat 1: What happens first
- Beat 2: The turning point
- Beat 3: How it ends / hook to next scene
---
### Change Log
| Date | Change |
|------|--------|
| YYYY-MM-DD | Initial outline created. |
| YYYY-MM-DD | Chapter 3 added, CharacterB route expanded. |
CHARACTER_DESIGN.md — Character Profiles
Path: docs/narrative/CHARACTER_DESIGN.md
Mandatory: Yes
One section per character. Covers protagonist, romanceable characters, and key supporting cast.
# CHARACTER_DESIGN.md — [Project Title]
---
## Protagonist: [Name]
### Identity
| Field | Value |
|-------|-------|
| **Name** | Full name (and nickname if applicable) |
| **Age** | Age range |
| **Role in story** | Their job, situation, or reason for being in this world |
| **One-sentence essence** | What defines them at their simplest |
| **Narrative lens** | Their profession/hobby shapes how they narrate (photographer notices light, musician notices rhythm, etc.) |
### Personality
- **Trait 1:** Description.
- **Trait 2:** Description.
- **Flaw:** What the story challenges in them.
- **Contradiction:** Something that doesn't match first impressions.
### Backstory
> A short paragraph about what shaped them before the story began.
### Arc
- **What they learn:** [ ]
- **What they gain:** [ ]
- **What they lose or give up:** [ ]
---
## Romanceable: [Character Name]
### Identity
| Field | Value |
|-------|-------|
| **Name** | Full name |
| **Age** | Age range |
| **Role in story** | Their position in the world |
| **Archetype** | [Deredere / Tsundere / Kuudere / etc.] |
| **One-sentence essence** | Who they are at their simplest |
| **Contradiction** | Something that doesn't match their surface |
### Appearance
> A short paragraph or bullet list of notable physical traits.
### Personality
- **Core trait:** What drives them.
- **Voice:** How they speak (register, sentence length, verbal habits, nicknames for the protagonist).
- **Backbone:** The formative event or relationship that shaped them.
- **Fear:** What they're afraid of.
- **Desire:** What they want (possibly even from themselves).
### Arc
| Stage | Description | Chapter |
|-------|-------------|---------|
| **Initial state** | How they are when first met | Ch1 |
| **First crack** | When the protagonist first sees beneath the surface | Ch[ ] |
| **Turning point** | When their arc pivots | Ch[ ] |
| **Climax** | The emotional peak of their route | Ch[ ] |
| **Final state** | How they are at story's end | Ch[ ] |
### Intimacy Style
| Dimension | Description |
|-----------|-------------|
| **Approach** | Eager / hesitant / commanding / yielding |
| **Verbal during sex** | Talkative / silent / commanding / whispering |
| **Emotional openness** | How vulnerable they are willing to be |
| **Post-coital behavior** | What they do after — cling, withdraw, talk, sleep |
| **Consent style** | How they communicate yes (enthusiastic, reluctant, through action) |
### Relationships
| Character | Dynamic |
|-----------|---------|
| [Protagonist] | How they relate to the protagonist |
| [Other character] | How they relate to other cast members |
---
## Supporting: [Character Name]
| Field | Value |
|-------|-------|
| **Name** | Full name |
| **Role** | Comic relief / mentor / rival / etc. |
| **Memorable trait** | What makes them stick in the player's mind |
| **Function** | What narrative purpose they serve |
| **Voice** | How they speak, in one sentence |
| **Relation to protagonist** | [ ] |
---
### Change Log
| Date | Change |
|------|--------|
| YYYY-MM-DD | Initial character profiles created. |
WORLD_BUILDING.md — Setting & Atmosphere
Path: docs/narrative/WORLD_BUILDING.md
Mandatory: Yes
Defines the world in sensory, structural, and social terms.
# WORLD_BUILDING.md — [Project Title]
---
## World Overview
> A paragraph describing the world in its broadest strokes. What kind of place is this? What's the season? What's the dominant feeling of being here?
---
## Geography
### Key Locations
| Location | Description | Mood | Key Scenes |
|----------|-------------|------|------------|
| [Location name] | What it looks like, feels like, where it is | [Warm / Tense / Intimate / etc.] | Ch1 Scene 2, Ch3 Scene 1 |
### Map
> A text-based or described layout of how locations connect. No visual map needed — describe the relationships:
> "The festival grounds sit between the river to the east and the main road to the west. The food stalls line the south edge. The performance stage is at the center, with the backstage area behind a row of equipment trucks to the north."
---
## Rhythm
### Daily / Seasonal Cycle
> How time flows in this world. School bells, festival schedules, work shifts, seasons, holidays.
- **Morning:** [What happens, what it feels like]
- **Afternoon:** [What happens, what it feels like]
- **Evening:** [What happens, what it feels like]
- **Night:** [What happens, what it feels like]
- **Special days:** [Festivals, holidays, recurring events]
---
## Rules & Social Norms
| Domain | Rule / Norm | Notes |
|--------|-------------|-------|
| **Social hierarchy** | Who has authority, who defers to whom | [ ] |
| **Traditions** | Rituals, ceremonies, customs the cast observes | [ ] |
| **Taboos** | What is not done, not spoken, not acknowledged | [ ] |
| **Unspoken rules** | Things everyone knows but nobody says | [ ] |
---
## Sensory Atmosphere
### Recurring Sensory Motifs
| Sense | Motif | Where It Appears |
|-------|-------|------------------|
| **Sight** | [Light quality, colors, visual signature] | Ch1, Ch3, Ch5 |
| **Sound** | [Ambient sound, silence, specific noise] | Ch2, Ch4 |
| **Smell** | [Location-specific scent] | Ch1, Ch6 |
| **Touch** | [Temperature, texture, humidity] | Ch3, Ch7 |
| **Taste** | [Food, drink, recurring flavor] | Ch1, Ch4 |
### Location Atmosphere Tags
| Location | Sensory Tags |
|----------|--------------|
| [Location] | golden hour, warm amber pools of light, long soft shadows, cicadas humming, smell of grass and dust |
| [Location] | cool blue night, moonlight filtering through windows, deep shadows, distant music, silence between crickets |
---
### Change Log
| Date | Change |
|------|--------|
| YYYY-MM-DD | Initial worldbuilding created. |
ROUTES_AND_CHOICES.md — Branching & Affinity
Path: docs/narrative/ROUTES_AND_CHOICES.md
Mandatory: Yes
Tracks every character route, affinity threshold, choice, and branching path. The technical backbone for implementing branching in any engine.
# ROUTES_AND_CHOICES.md — [Project Title]
---
## Affinity System Overview
| Character | Variable Name | Default | Range | Route-lock Threshold |
|-----------|---------------|---------|-------|---------------------|
| [CharacterA] | `CharacterA.affinity` | 0 | -10 to +10 per chapter | ≥ 8 at Ch4 end |
| [CharacterB] | `CharacterB.affinity` | 0 | -10 to +10 per chapter | ≥ 6 at Ch4 end |
**Notes:** Affinity is hidden from the player. Route lock-in happens at [chapter].
---
## Chapter-by-Chapter Affinity Map
### Chapter 1: [Title]
| Scene | Choice | Option A | Option B | Option C |
|-------|--------|----------|----------|----------|
| Scene 1 | "Choice title" | A+2, B-1 | B+1 | Neutral |
| Scene 3 | "Choice title" | A+3 | A+1, B+1 | A-2 |
**Maximum gain this chapter:** A: +5, B: +2 \| **Maximum loss:** A: -3, B: -1
**Chapter-end thresholds:**
- A ≥ 4: [Scene variant — what changes]
- B ≥ 2: [Scene variant — what changes]
- A ≤ -2: [Negative consequence]
### Chapter 2: [Title]
...
---
## Route Branching Map
\`\`\`
┌── Scene A1 ──┐
│ │
Ch1 ── Ch2 ── Ch3 ──┤ ├── Ch5 (Route A) ── Ch6 ── Ending A
│ │
└── Scene B1 ──┘
│ │
└── Scene B2 ──┘── Ch5 (Route B) ── Ch6 ── Ending B
\`\`\`
### Route A: [CharacterA]
| Chapter | Lock-in? | Key Choice | Affinity Required |
|---------|----------|------------|-------------------|
| 1 | No | [Choice] | — |
| 2 | No | [Choice] | — |
| 3 | No | [Choice] | A ≥ 3 |
| 4 | **Yes** | [Lock-in choice] | A ≥ 8 |
| 5 | — | [Route-specific choices] | — |
| 6 | — | [Final choice] | — |
### Route B: [CharacterB]
...
---
## Choice Catalog
### Chapter 1
#### Choice 1 — "[Choice text]"
| | Option | Affinity | Scene Consequence | Future Impact |
|--|--------|----------|-------------------|---------------|
| A | "[Option text]" | A+2 | CharacterA smiles, opens up | Unlocks Ch3 variant A |
| B | "[Option text]" | B+1 | CharacterB notices, files it | Unlocks Ch4 scene B |
| C | "[Option text]" | None | Scene continues neutrally | — |
**Narrative intent:** [Why this choice exists and what it communicates to the player]
#### Choice 2 — "[Choice text]"
...
---
## Scene Variants
| Scene | Trigger | Variant Content |
|-------|---------|-----------------|
| Ch3 Scene 2 | A ≥ 4 | CharacterA joins protagonist for the walk home alone |
| Ch3 Scene 2 | B ≥ 3 | CharacterB appears instead, awkward encounter |
| Ch3 Scene 2 | Neither | Protagonist walks alone, internal monologue |
---
### Change Log
| Date | Change |
|------|--------|
| YYYY-MM-DD | Initial route structure created. |
EROTIC_CONTENT.md — Intimacy Tracking (Optional)
Path: docs/narrative/EROTIC_CONTENT.md
Mandatory: No (only for projects with explicit content)
Tracks where each route stands in the five-stage intimacy model, what scenes exist, and content notes.
# EROTIC_CONTENT.md — [Project Title]
---
## Route Overview
| Character | Stage 1 | Stage 2 | Stage 3 | Stage 4 | Stage 5 | Notes |
|-----------|---------|---------|---------|---------|---------|-------|
| [CharacterA] | Ch1–2 | Ch3 | Ch4–5 | Ch6 | Ch7 | Slow-burn, consent is gradual |
| [CharacterB] | Ch1 | Ch2–3 | Ch4 | Ch5 | Ch6 | Faster escalation, more explicit |
---
## Stage Details
### [CharacterA] — Stage 1: Attraction (Ch1–2)
| Scene | Chapter | Content | Consent Cue |
|-------|---------|---------|-------------|
| [Scene name] | 1 | Accidental touch, charged glance, awareness | — (pre-consent stage) |
| [Scene name] | 2 | Almost-kiss interrupted | CharacterA doesn't pull away |
**Notes:** Keep this stage entirely non-explicit. Build tension through proximity and eye contact.
### [CharacterA] — Stage 2: Tension (Ch3)
| Scene | Chapter | Content | Consent Cue |
|-------|---------|---------|-------------|
| [Scene name] | 3 | First kiss | CharacterA initiates |
**Notes:** The kiss is emotional, not just physical. Aftermath is essential.
### [CharacterA] — Stage 3: Escalation (Ch4–5)
| Scene | Chapter | Content | Consent Cue |
|-------|---------|---------|-------------|
| [Scene name] | 4 | Undressing, manual stimulation | Verbal "yes" |
| [Scene name] | 5 | Oral sex | Both initiate |
### [CharacterA] — Stage 4: Consummation (Ch6)
| Scene | Chapter | Content | Consent Cue |
|-------|---------|---------|-------------|
| [Scene name] | 6 | Full intercourse, multiple positions | Verbal confirmation, eye contact |
**Notes:** Aftermath scene is [scene name]. Do NOT end at climax.
### [CharacterA] — Stage 5: Aftermath (Ch7)
| Scene | Chapter | Content |
|-------|---------|---------|
| [Scene name] | 7 | Morning after, pillow talk, emotional vulnerability |
**Notes:** This is where the emotional weight of the route lands. The intimacy is conversational as much as physical.
---
## Consent Framework
| Character | Consent Style | Notes |
|-----------|---------------|-------|
| [CharacterA] | Enthusiastic verbal | She says what she wants, clearly |
| [CharacterB] | Reluctant → action-based | Words fail her; consent is in touch and presence |
**General rule:** All explicit scenes begin with an unambiguous moment of consent appropriate to the character. No scene ends at climax — aftermath is mandatory.
---
## Content Boundaries
- **On-screen penetration:** [Yes / No / Context-dependent]
- **Nudity detail level:** [Suggestive / Partial / Full anatomical]
- **Euphemism policy:** [Sensory-specific language / Soft euphemisms / Mixed]
- **Taboo content included:** [List any, with content notes]
- **Off-screen:** [What is implied rather than shown]
---
### Change Log
| Date | Change |
|------|--------|
| YYYY-MM-DD | Initial erotic content tracking created. |
1. Story Architecture
The Three-Act Structure (with Branching)
Most VN narratives fit a modified three-act structure, where branching replaces the linear second act:
Act I — Setup (25% of story)
- Establish protagonist, world, tone
- Introduce main characters and their dynamics
- First encounters with each romanceable character
- First major choice with meaningful consequences
- Ends with the "point of no return" — the protagonist commits to staying in this world
Act II — Branching (50% of story)
- Routes diverge based on player choices
- Each route explores a different character's arc
- Midpoint: a revelation or crisis that deepens the relationship
- Rising intimacy: from attraction through tension to consummation
- Ends with the climactic choice (route lock-in or final emotional test)
Act III — Resolution (25% of story)
- The consequences of the climax play out
- Emotional resolution for the chosen route
- The other characters get closure (or remain unresolved — bittersweet)
- Endings should feel earned by the choices that led there
Common VN Story Shapes
| Shape | Description | Example Pattern |
|---|---|---|
| Summer Romance | Finite time together; the relationship has an expiration date. The question is whether to love fully despite the inevitable end. | Festival circuit, study abroad, vacation fling |
| Slow Trust | One character is guarded or hostile. The player must earn access through patience and restraint, not pursuit. | Tsundere route, damaged character, rival-to-lovers |
| Rising Stakes | An external threat or timer forces intimacy to develop under pressure. | Mystery plot, competition, deadline |
| Found Family | A group of strangers becomes a temporary family. The romance is part of a larger belonging. | Road trip, shared workplace, traveling troupe |
| Forbidden | Social, professional, or supernatural barriers to the relationship. The tension is in the transgression. | Teacher/student, royalty/commoner, arranged marriage |
Chapter Structure
Each chapter should have:
- A clear emotional arc — start at one emotional state, end at a different one
- A central question — what is this chapter about? (e.g., "Can the protagonist earn Christy's trust?" or "What is Emma hiding?")
- 2–4 meaningful choices — not every scene needs one, but every chapter should advance the player's sense of agency
- A hook for the next chapter — a question raised, a tension unresolved, a character's expression that lingers
- A shift in the relationship — by chapter's end, the dynamic between protagonist and each main character should be measurably different from where it started
2. Character Design
The Protagonist
The VN protagonist is the player's avatar. Design guidelines:
- They must have enough personality to be interesting but not so much that the player can't project onto them. A blank slate is boring; a fully defined character robs the player of agency.
- Give them one strong trait that frames their perspective. Examples: a photographer (sees the world in frames and light), a writer (notices details and metaphors), a musician (thinks in rhythm and harmony), a chef (understands through taste and texture).
- Their profession/hobby shapes how they narrate. A photographer notices composition, light, and moments. A writer notices dialogue and subtext. A musician notices rhythm and silence. Use this lens consistently in narration.
- They should have a flaw that the story challenges. Arrogance, fear of intimacy, running from the past, workaholism, people-pleasing. The romance should force them to confront it.
The Romanceable Characters
Each romanceable character needs:
Core Identity — Who are they at their simplest?
- Archetype (tsundere, deredere, kuudere, etc.) as a starting point, not a cage
- One sentence that captures their essence: "She's someone who has never been photographed by someone she trusts."
- A contradiction: something about them that doesn't match first impressions
Backbone — What shaped them?
- One formative event from their past (not a tragic monologue — a real, specific memory)
- A relationship that defined them (parent, mentor, rival, lost friend)
- A fear they carry
- A desire they may not even admit to themselves
Voice — How do they speak?
- Verbal register (formal? casual? slangy? dated?)
- Sentence length (long and flowing? short and clipped?)
- What they say vs. what they don't say (tsundere hides affection; kuudere speaks plainly and lets the words land)
- A recurring verbal habit (a nickname for the protagonist, a favorite phrase, a tendency to trail off)
Arc — How do they change?
- What do they learn? What do they get?
- What do they lose or give up?
- The romance should cost them something meaningful
Intimacy Style — How do they approach physical and emotional closeness?
- Are they eager or hesitant? Verbally expressive or silent? Teasing or earnest?
- Does intimacy come easily (deredere) or is it hard-won (tsundere)?
- How do they change after sex — more open, more vulnerable, more guarded in a different way?
Character Archetype Reference
A starting palette — each archetype suggests a psychology, a relationship arc, and an intimacy style. The word "-dere" comes from the Japanese "deredere" (でれでれ), meaning "lovey-dovey" or "lovestruck." The prefix modifies this core: tsun- (aloof/irritable), yan- (mentally ill, from yanderu), kuu- (cool, from kuuru), dan- (shy, from danmari — silent), baka- (stupid), sado- (sadistic), hima- (princess/hime), haji- (embarrassed).
Use these as a starting palette, not a cage. The best characters transcend their archetype — they have specific traits, contradictions, and details that make them feel like people rather than categories.
Main Archetypes
Deredere — "Lovey-Dovey"
The only archetype that has no abbreviation from the base term "deredere" — its definition is the root meaning: lovey-dovey.
| Dimension | Description |
|---|---|
| Core Psychology | A Deredere is openly, unguardedly affectionate. They are kind and energetic, seen most of the time in a cheerful and happy mood, and tend to spread joy to those around them. Whatever happens, they quickly return to showing off their smile. They are not afraid to show their care and affection to their love interest. They do not find it strange for another character to get along with the person they love — as long as the loved one is happy, a Deredere will not get too down, whether they themselves end up in a relationship with that person or not. They will even be kind to their rivals and have fun with them in the meantime. |
| Why They're Like This | Their love is not possessive or transactional. It flows outward freely without expectation of return. This is not naivety — it's a radical form of emotional generosity. |
| Relationship Arc | They are either completely open about their feelings, confessing right away, or they take a little longer to confess due to the other person's reluctance (not their own). The dramatic question on their route is not "will they admit their feelings?" but rather "will their love be returned before circumstances separate them?" The obstacles are external, not internal. |
| Intimacy Style | Eager, verbally expressive, affectionate — intimacy is a natural extension of who they are. They do not hold back during sex; they praise, reassure, and tease gently. The emotional vulnerability is not in the act itself but in how much they are risking by loving so openly. |
| Speech Patterns | Uses nicknames, laughs easily, asks genuine questions, emotionally direct. Calls the protagonist by a pet name from early on. |
| Canonical Examples | Meiko "Menma" Honma (Anohana), Chika Takami (Love Live! Sunshine!!), Madoka Kaname (Puella Magi Madoka Magica), Chiyo Sakura (Gekkan Shoujo Nozaki-kun), Rinko Yamato (Ore Monogatari) |
Tsundere — "Aloof then Loving"
From tsun- (tsuntsun — aloof, irritable) + deredere (loving). Originated in bishōjo games; now a core moe archetype across all anime and manga media.
| Dimension | Description |
|---|---|
| Core Psychology | A Tsundere is outwardly strict, cold, and sometimes hostile toward the person they like. They hide their feelings because they are shy, nervous, insecure, or simply unable to behave properly in front of their crush. They alternate between two distinct moods: tsuntsun (aloof or irritable) and deredere (loving). A Tsundere pretends not to be interested in someone else, yet continues to do things for that person. They keep saying they are actually not interested — even as their actions prove otherwise. |
| Why They're Like This | Vulnerability is terrifying to a Tsundere. Admitting they want something means risking rejection, looking foolish, or losing control. The hostility is a fortress. The kindness that slips through — a meal prepared, a worried glance, an object retrieved — is the real self emerging despite the walls. |
| Relationship Arc | The arc progresses in layers. Early stages are almost entirely tsun: dismissive, cold, corrective. Over time, cracks appear in the fortress — a favor done without being asked, a moment of concern, a rare compliment disguised as criticism. The deredere emerges gradually and is always followed by a compensatory tsun backlash. The final stage is the full admission of love, often reluctant, embarrassed, or shouted as if it's an accusation. |
| Intimacy Style | Reluctant, commanding, protective. They maintain control by directing the encounter. Vulnerability leaks in fragments: a whispered admission, a hand that grips too tightly, a moment of stillness where the mask drops. Post-coital silence is meaningful — they are processing having been seen. They may push the protagonist away immediately after, then pull them back. |
| Speech Patterns | Terse, dismissive, rarely offers direct compliments. Extremely frequent phrases: "It's not like I like you or anything!" and "Don't get the wrong idea!" Often calls the love interest "baka" (stupid/idiot) in a gentler way. Warmth is in what they don't say — in the silences, the unfinished sentences, the things they do instead of saying. |
| Canonical Examples | Rin Tohsaka (Fate/Stay Night), Asuka Langley (Neon Genesis Evangelion), Taiga Aisaka (Toradora!), Mikoto Misaka (A Certain Scientific Railgun), Chitoge Kirisaki (Nisekoi) |
Kuudere — "Cool then Loving"
From kuu- (kuuru, Japanese adaptation of English "cool") + deredere. Kuuru can mean someone seems cool, calm, cold, or capable of handling any situation.
| Dimension | Description |
|---|---|
| Core Psychology | A Kuudere has a calm and peaceful personality that never panics. They show few emotions and, in extreme cases, are completely devoid of them — but they may hide their true feelings deep down. They are cold, blunt, and cynical on the surface; on the inside they are very caring, at least when it comes to those they love. They seem inexpressive, do not react to what the love interest says, do not laugh often at jokes, and are very often associated with the stereotype of the genius detached from the world. They are often characterized by white, blue, or other cool-colored hair. |
| Why They're Like This | The Kuudere's coolness is not a wall like the Tsundere's hostility — it is a genuine temperament. They are not hiding warmth behind ice; they simply are cool. The warmth is not a suppressed truth but a growth that happens when someone finally reaches them. The "melt" is real and transformative. |
| Relationship Arc | As the relationship develops, the Kuudere begins to open up and show expressions — a slight smile, a rare laugh. In some cases, they will completely "melt" or break their ice armor, starting to cry profusely or shout "I love you" to their crush. This shift from kuu- mode to -dere mode is the emotional climax of their route. |
| Intimacy Style | Rare emotional breaks are devastating. During sex, they may remain outwardly composed until a specific moment shatters their control — a touch in the right place, a word at the right time — and the release is overwhelming. Afterward, they may be unusually vulnerable, talkative, or clingy, as if the ice has genuinely melted. The contrast between their usual composure and their intimate vulnerability is what makes the scene powerful. |
| Speech Patterns | Few words, plain speech, no embellishment. Calm, monotone delivery. They appear unaffected by the world around them — never overly happy, excited, surprised, sad, annoyed, or angry. Extreme examples can seem as emotionless as robots. Despite their seriousness, they often have an excellent sense of sarcastic humor that catches people off guard. |
| Canonical Examples | Kanade "Angel" Tachibana (Angel Beats!), Homura Akemi (Puella Magi Madoka Magica), Yotsugi Ononoki (Monogatari Series), Mei Misaki (Another), Mai Minakami (Nichijou) |
Dandere — "Silent then Loving"
From dan- (danmari — silence, not speaking) + deredere.
| Dimension | Description |
|---|---|
| Core Psychology | A Dandere has a quiet, peaceful, but asocial personality. They are afraid to speak, as they fear that everything they say may get them into trouble. Because of this quiet and silent personality, they often appear devoid of emotions. However, they tend to suddenly become talkative, sweet, and cute when alone with the right person, if they are comfortable enough to pour out their heart. They are not actually emotionless or cool — they are shy. The silence is social anxiety, not composure. |
| Why They're Like This | The Dandere's silence is fear-based: fear of saying the wrong thing, of being judged, of drawing attention. They do not avoid conversation because they are cold — they avoid it because they care too much about what others think. The irony is that they have rich inner lives and deep feelings; they simply cannot access them in front of other people. |
| Relationship Arc | A Dandere will behave more or less like a normal person but will not speak unless spoken to or asked. They will avoid speaking because of their shyness, but if necessary they will speak, sometimes with some difficulty or embarrassment. They tend to feel more at ease when surrounded by more people (since they have fewer occasions to speak) and relax when new characters are introduced (putting them on the same level as everyone else). The arc is about earning enough trust that the protagonist becomes one of the people with whom they can be talkative — the "safe person." |
| Intimacy Style | Whispered, hesitant, easily overwhelmed. They need the other person to lead physically and verbally. They may be non-verbal during sex, communicating through touch and breath rather than words. Afterward, when the vulnerability of intimacy cracks their shell, they may become unexpectedly talkative — the floodgates open. This post-coital confession of inner thoughts is the reward of their route. |
| Speech Patterns | Soft-spoken, trails off, apologizes readily, takes time to formulate thoughts. Becomes agitated if invited to speak publicly. They stutter, repeat themselves, or give one-word answers. Alone with the safe person, they suddenly have opinions, stories, jokes, and observations — a completely different person emerges. |
| Canonical Examples | Mio Akiyama (K-ON!), Nagisa Furukawa (Clannad), Nadeko Sengoku (Monogatari Series), Umi Sonoda (Love Live!), Hitori Bocchi (Hitoribocchi no Marumaru Seikatsu) |
Distinction from Kuudere: A Dandere becomes nervous (not calm) in social situations with their crush and prefers to remain silent. A Kuudere can still speak while maintaining composure and calm. A Dandere becomes agitated if invited to speak; a Kuudere has no problem answering if necessary.
Bakadere — "Stupid then Loving"
From baka (stupid, idiot, imbecile) + deredere.
| Dimension | Description |
|---|---|
| Core Psychology | A Bakadere has a very clumsy and stupid personality, most of the time lacking common sense. They are for the most part very innocent and sweet, but their stupidity overshadows their other attributes. Most tend to be excessively carefree and optimistic due to their lack of intelligence. They act in a childish and empty-headed way, rushing into things without thinking first, resulting in embarrassing situations. |
| Why They're Like This | The stupidity is not a flaw — it's a shield and a gift. Because they don't overthink, they experience the world with unfiltered joy. They do not dwell on embarrassment, do not hold grudges, and do not second-guess their feelings. Their honesty is not a choice — it's the only way they know how to be. This can make them surprisingly wise in moments of simplicity. |
| Relationship Arc | The route is about whether the protagonist can take them seriously enough to see the real person underneath the chaos. Moments of unexpected sincerity — a genuine observation, a caring act, a moment of stillness — reveal that the Bakadere is not actually stupid; they simply operate on a different, more intuitive logic. The climax often involves the Bakadere doing something unexpectedly competent or profound, shocking everyone. |
| Intimacy Style | Chaotic, eager, prone to accidents even during intimacy. Unexpected sincerity breaks through the clumsiness at crucial moments. They may say something startlingly tender right after tripping over their own feet. The emotional weight comes from the contrast — the serious moment that cuts through the noise. |
| Speech Patterns | Rapid, unfiltered, forgets words, goes on tangents mid-conversation. Talks to inanimate objects. Apologizes for things that aren't their fault. Calls things by the wrong name. Their sincerity catches the listener off guard because it emerges without warning from the chaos. |
| Canonical Examples | Chika Fujiwara (Kaguya-sama: Love is War), Mankanshoku Mako (Kill la Kill), Sasha Blouse (Attack on Titan), Mashiro Shiina (The Pet Girl of Sakurasou), Yuuko Yoshida (Machikado Mazoku) |
Yandere — "Sick then Loving"
From yan- (yanderu — to be mentally ill) + deredere.
| Dimension | Description |
|---|---|
| Core Psychology | A Yandere initially loves and cares for the person for whom they harbor a strong affection — until their romantic love, admiration, and devotion become exuberant, excessive, and mentally unstable through overprotection, violence, brutality, or a combination of the three. They are not stupid or reckless, but rather possessive and jealous — they would kill to be alone with their beloved. Yanderes are hopelessly in love, which drives obsessive behavior against anyone perceived as a threat. |
| Why They're Like This | The origin varies: some were victims of a horrible event that broke something inside them; others simply had a natural inclination toward extreme possessiveness. Some are undeniably crazy from the very beginning. Regardless, they have a mentally ill type of love — love as consumption, as ownership, as the only thing that makes the world make sense. The beloved is not a partner but an anchor to sanity. |
| Relationship Arc | The arc moves from sweet devotion through growing possessiveness to open threat. Early stages are indistinguishable from genuine warmth and care. The shift happens when a perceived rival appears or when the protagonist's independence threatens the Yandere's sense of ownership. The climax is a confrontation where the Yandere's true nature is fully revealed — and the protagonist must choose acceptance, reformation, or escape. |
| Intimacy Style | Possessive devotion. Intimacy triggers both tenderness and the fear of losing the person. During sex, the language is possessive: "mine," "yours," "no one else." The line between passion and violence is thin — a grip that bruises, a kiss that borders on biting. Aftercare is crucial: the Yandere needs reassurance of belonging. |
| Speech Patterns | Sudden tonal whiplash — sweet and loving to cold and threatening within a single sentence. Possessive language dominates: "you're mine," "I won't let anyone take you," "if you leave me..." The sweetness is genuine; it's the conditions attached to it that are terrifying. In the early stages, they sound like a normal, affectionate person. |
| Canonical Examples | Yuno Gasai (Mirai Nikki), Misa Amane (Death Note), Kotonoha Katsura (School Days), Shion Sonozaki (Higurashi no Naku Koro ni), Anna Nishikinomiya (Shimoneta) |
Subtypes: Some Yandere are aware of their condition and struggle against it; others embrace it. Some are triggered by specific events; others are always this way. Choose the subtype that serves your story.
Sadodere — "Sadistic then Loving"
From sado- (sadomaso — sadomasochism) + deredere.
| Dimension | Description |
|---|---|
| Core Psychology | A Sadodere has a sadistic personality. They enjoy playing with the feelings of their love interests and are commonly referred to as "teasers." They are troublemakers who enjoy manipulating the feelings of others, usually deriving pleasure from it. They play with the emotions of their love interests and enjoy humiliating them. They are typically defined by their sadistic tendencies, can be violent and cruel to others and even more so to their loved ones, and always have a severe lack of empathy. However, some Sadodere can redeem themselves. |
| Why They're Like This | The Sadodere finds emotional and sometimes physical pain pleasurable — specifically, the pain of others, and most specifically, the pain of someone they care about. The cruelty is a form of intimacy: they only play with people who matter. The pleasure comes from seeing a reaction, knowing they have power, and being the cause of someone's vulnerability. The redemption arc involves learning that causing pain is not the same as feeling connection. |
| Relationship Arc | Early stages are teasing, humiliation, and emotional manipulation disguised as playfulness. The protagonist must endure, push back, or play along. The mid-point reveals the vulnerability beneath the sadism — the Sadodere is cruel because they fear genuine connection. The climax is either redemption (learning intimacy without cruelty) or mutual acceptance (a relationship that accommodates their nature within consensual boundaries). |
| Intimacy Style | Dominant, playful, testing boundaries. They derive pleasure from the protagonist's reaction — the more intense, the better. Their cruelty in bed is a form of attention, of seeing the other person's responses intimately. If redeemed, intimacy can shift to genuine tenderness that surprises even them. If not redeemed, the line between consensual power play and genuine harm blurs. |
| Speech Patterns | Teasing, condescending, mocking in a way that sounds playful but carries an edge. They call the protagonist amusing names, laugh at their embarrassment, and poke at insecurities with surgical precision. The tone is light, even cheerful, while the content is cutting. |
| Canonical Examples | Kurumi Tokisaki (Date A Live), Junko Enoshima (Danganronpa), Himiko Toga (My Hero Academia), Hayase Nagatoro (Don't Toy with Me, Miss Nagatoro), Maika Sakuranomiya (Blend S) |
Distinction from Yandere: A Sadodere enjoys doing harm (the act itself is pleasurable). A Yandere will hurt others only to prevent them from stealing their crush (the harm is instrumental, not pleasurable). A Yandere may hurt their love interest, but only to get something out of it, without necessarily feeling satisfaction from those actions.
Genki — "Energetic"
Not strictly a -dere type, genki (元気) means "energetic, healthy, lively." Often overlaps with Deredere but is distinct: a Genki character's energy is general (not specifically romantic), and their positivity can mask deeper insecurity.
| Dimension | Description |
|---|---|
| Core Psychology | A Genki character is defined by boundless energy, enthusiasm, and a relentlessly positive outlook. They are loud, expressive, and physically active — always moving, always talking, always doing. Unlike the Deredere (whose warmth is specifically romantic), the Genki is energetic about everything: food, hobbies, friends, competition, life itself. The energy can be genuine joy or a carefully maintained mask for sadness, loneliness, or insecurity. |
| Why They're Like This | Two common origins: either they genuinely experience the world as exciting and wonderful (pure Genki), or they are afraid of stillness because stillness means thinking about things they don't want to face (defensive Genki). The second type is more dramatically interesting — the energy is a performance that cannot be sustained forever. |
| Relationship Arc | The arc involves the protagonist seeing past the energy to whatever lies beneath. For a pure Genki, the challenge is keeping up with them. For a defensive Genki, the arc is about earning the trust that lets them stop performing — the quiet, vulnerable person beneath the noise. The most powerful moment is when a Genki character goes silent. |
| Intimacy Style | Enthusiastic, vocal, physically active. May laugh during sex, make jokes, or treat it as another adventure. When a defensive Genki quiets down during intimacy, it signals that they have dropped the mask — this is more intimate than anything physical. Afterward, they may be clingy or quietly tearful, depending on what they were hiding. |
| Speech Patterns | Interrupts, bounces between topics, exclamation-heavy. Talks with their hands. Laughs loudly and often. Uses exaggerated language ("the best ever!" "absolutely incredible!"). Silence from a Genki is a red flag — something is very wrong. |
| Canonical Examples | Yui Hirasawa (K-ON!), Ruby Kurosawa (Love Live! Sunshine!!), Naruto Uzumaki (Naruto), Lina Inverse (Slayers), Mako Mankanshoku (Kill la Kill) |
Minor / Niche Archetypes
These archetypes are less common as primary romance routes but can define supporting characters, comic relief, or unique route flavors in adult VNs. Use them sparingly and specifically.
| Archetype | Meaning | Core Trait | Narrative Function | Notes |
|---|---|---|---|---|
| Himedere | Hime (princess) + dere | Demands to be treated like royalty — but only by the person they love (unlike Oujodere who demands it from everyone). | A route about earning the right to be their equal. Surrendering control is the ultimate gift. | Elaborate vocabulary, commanding tone. Intimacy is where they let someone lead for the first time. |
| Hajidere | Haji (embarrassment) + dere | Becomes extremely nervous and embarrassed in front of the person they love. Blushes constantly, fumbles words, avoids eye contact. | A gentle, slow-burn route about building comfort, not passion. Every small milestone (holding hands, first kiss) is a major victory. | Less dramatic than Dandere — they WANT to connect but their own embarrassment is the obstacle. |
| Mayadere | Mayu (dance/deceive) + dere | Initially dangerous or antagonistic, switches sides for love. The "enemy turned lover." | A redemption arc where love is the catalyst for changing allegiances. High drama, high stakes. | Requires the protagonist to trust someone who has been against them. The betrayal/redemption pivot is the climax. |
| Byoukidere | Byouki (illness) + dere | Extremely kind and sweet, but suffers from a physical or mental illness, most of the time fatal. | A tragic route where love exists under a time limit or against medical reality. The question is whether to love despite the inevitable loss. | Handle with care — the illness should not be the character's only trait. They are a person first, a patient second. |
| Shundere | Shun (melancholy/depressed) + dere | Always sad and depressed due to various life misfortunes. | A route about being the light that helps someone heal. Requires patience — the character may resist happiness because they've forgotten how to feel it. | Avoid romanticizing depression. The arc should be about genuine growth, not being "fixed" by love. |
| Kamidere | Kami (god/goddess) + dere | Wants to be treated like a god or goddess. Grandiose, demanding, looks down on others. | A comeuppance arc about humility, or a power-fantasy route where the protagonist accepts their worship. | Similar to Himedere but writ larger — the demand is for worship, not just royal treatment. |
| Goudere | Gou (strong/wild) + dere | Would stop at nothing to make their "master" happy. Devoted to the point of absurdity. | Comic relief or a dark satire of devotion. Their efforts are disproportionate, ill-advised, or self-destructive. | The comedy comes from how seriously they take their role. Their dedication is genuine, their execution is disaster. |
| Nemuidere | Nemui (sleepy) + dere | Spends most of their time sleeping and lazing about. Rarely fully awake or present. | A laid-back, low-stakes route. Energy is precious and rare — when they wake up for the protagonist, it means something. | Often used for comic effect, but the sleeping can mask exhaustion from an unseen burden (see: Byoukidere overlap). |
| Hiyakasudere | Hiyakasu (to tease/ridicule) + dere | Marked hypersexuality and histrionic personality. Flirts brazenly and constantly, often as a performance. | A route about whether their sexual confidence is real or a mask for deeper insecurity. The protagonist must decide if they want the performance or the person beneath it. | Distinct from Sadodere: a Hiyakasudere is performatively sexual rather than sadistic. The cruelty, if any, is incidental. |
| Kanedere | Kane (money) + dere | Attracted to rich people or people with lots of money. Romance is transactional, at least initially. | A route about learning the difference between value and price. The character's materialism is a shield or a learned behavior that must be unlearned. | Risk of making the character unlikable. The key is showing why they value money — and what they actually value beneath it. |
| Kekkondere | Kekkon (marriage) + dere | Wants to immediately marry someone they have just met. Commitment-obsessed from day one. | A comedy route or a tragically rushed romance. The character's urgency about marriage is either endearing or alarming. | Often paired with Genki or Bakadere energy. The protagonist spends the route either gently slowing them down or being swept away. |
| Oujidere / Oujodere | Ouji (prince) / Ojo (princess) + dere | A narcissistic character who wants — and sometimes demands — to be treated like a prince or princess. Unlike Himedere, this extends to everyone, not just the love interest. | A character who must learn that the world does not revolve around them. The romance is a mirror that shows them their own selfishness. | More broadly arrogant than Himedere. The arc is about learning reciprocity. |
| Yottadere | Yotta (drunk) + dere | Loves drinking anything alcoholic. Alcohol is central to their personality and social interactions. | A comic relief character whose drinking is either a harmless quirk or a serious concern. The route may involve confronting dependency. | Use carefully — alcoholism as a cute quirk is tone-deaf unless the narrative acknowledges the seriousness. |
| Bocchandere | Bocchan (young master/son of wealthy family) + dere | Has a "dark" personality, often linked to the Yakuza, Mafia, or criminal underworld. A dangerous background that shapes their worldview and relationships. | A "bad boy/girl" route where the love interest's criminal ties create external conflict and internal moral questions. | The darkness should be integrated into the character's psychology, not just a surface aesthetic. |
The Supporting Cast
Side characters (friends, rivals, mentors, comic relief) need enough depth to feel real but not so much that they distract from the main romance:
- Each needs one clear function in the story (comic relief, wise advice, obstacle, alternate perspective)
- Each needs one memorable trait (a catchphrase, a ritual, a distinctive appearance detail)
- Their relationship to the protagonist should shift measurably based on route choices
- They can have their own quiet arcs that play out in the background
3. Worldbuilding
The "Small World" Principle
A visual novel doesn't need a fully realized fantasy world. It needs a small, vivid world that feels complete. Whether the setting is a school, a festival circuit, a spaceship, or a small town:
Define the world by three things:
- Geography — the physical spaces where scenes happen. Draw them. Name them. Know how they connect.
- Rhythm — the daily or seasonal cycle that structures life in this world. School bells, festival schedules, work shifts, seasons.
- Rules — social norms, unspoken hierarchies, traditions. What's expected? What's forbidden? What's sacred?
Show the world through details, not exposition:
- The cicada song that changes pitch at dusk
- The way a particular stall owner always saves the best ingredients for regulars
- The bench where everyone knows you can find [character] between classes
- The sound footsteps make on different floors of the school
The world should reflect the emotional state:
- A happy scene happens in golden-hour light with warm colors
- A tense scene happens in harsh midday sun or gray rain
- An intimate scene happens in a small, enclosed space (a booth, a corner, a room with a single lamp)
Creating Atmosphere
Atmosphere is the texture of the world — what it feels like to be in it. Build it through recurring sensory motifs:
| Sense | What to Describe | Example |
|---|---|---|
| Sight | Light quality, colors, movement, time of day | "The afternoon light slanted through the blinds in long, golden stripes." |
| Sound | Ambient noise, silence, specific recurring sounds | "Cicadas, always cicadas — a wall of sound that faded into the background until it stopped." |
| Smell | Location-specific scents, character scents, seasonal smells | "The air smelled of grilled meat and cheap incense and the particular sweetness of summer night." |
| Touch | Temperature, texture, humidity, pressure | "The humidity pressed against her skin like a second clothes." |
| Taste | Food, drink, the taste of a kiss or sweat | "The yakisoba was too salty and perfect and she ate it with her fingers." |
Pick 2–3 sensory threads per setting and return to them. They become the world's signature.
4. Branching & Choice Design
The Anatomy of a Choice
Every choice in a VN communicates three things simultaneously:
- What the protagonist does (surface action)
- What the protagonist values (character insight)
- Which character the player is prioritizing (route signal)
Choice Types
| Type | Description | Effect |
|---|---|---|
| Route Signal | Points toward one character | Affinity shift + scene access |
| Moral/Value | Tests the protagonist's character | Affects how others perceive them |
| Pacing | Controls the rhythm of a scene (rush vs. linger) | Changes scene detail, not outcome |
| Information | Player chooses what to notice or ask | Unlocks different context for future choices |
| Relationship | Deepens or distances an existing bond | Large affinity shift with one character |
| Lock-in | Irreversibly commits to a route | Closes other routes |
Choice Design Principles
-
Three options is the sweet spot. Two feels like a test. Four is overwhelming. Three allows: one leaning toward CharacterA, one toward CharacterB, and one that's reflective, neutral, or self-directed.
-
Every choice has stakes. No throwaway choices. Even the "safe" option changes something subtly — a character's perception, a future scene variant, a line of dialogue.
-
No morally obvious "correct" answer. The best choice for CharacterA is often the worst for CharacterB. The player's preference should determine what's "right," not a hidden morality scale.
-
Choice text communicates emotional direction. The player should be able to infer the stakes from the option text:
- "Reach for her hand" → clearly toward CharacterA
- "Wait and see what happens" → cautious/reflective
- "Catch his eye instead" → clearly toward CharacterB
-
Choices should feel meaningful in the moment, not just in retrospect. Even small affinity shifts should be accompanied by an immediate, visible character reaction (a smile, a frown, a silence).
-
Conditional choices (appearing only when affinity is high enough) reward investment. They signal that past choices have cumulative weight.
-
Not every scene needs a choice. Let some scenes breathe — pure character interaction without branching. Constant choices exhaust the player.
Branching Density
- Light branching — 1–2 choices per chapter, mostly flavor variants. Best for short, linear stories.
- Medium branching — 2–4 choices per chapter, affinity system with route-lock halfway through. Standard for most VNs.
- Heavy branching — 4–6 choices per chapter, multiple affinity axes, branching that compounds. Best for replayability-focused games.
5. Dialogue Craft
Naturalistic Dialogue in a Stylized Medium
VN dialogue is not real speech — it's compressed, heightened, meaningful. But it must feel natural. Key principles:
Compression — Characters say in three lines what real people would say in ten. Every line advances character, relationship, or plot.
Subtext — What characters don't say is often more important than what they do:
- "It's cold tonight" might mean "I want to be closer to you"
- "You're late" might mean "I was worried"
- "I don't care" always means the opposite
Character-specific vocabulary — Each character should have words and phrases the others don't use:
- One character might say "absolutely" where another says "sure"
- One character might use more metaphors; another might speak with blunt literalism
- Nicknames, pet names, and verbal tics are character identifiers
Rhythm and silence — Not every line needs a reply. Pauses, silences, and changes of subject communicate:
- A pause before answering suggests hesitation or dishonesty
- Changing the subject suggests discomfort
- Silence between two characters can be comfortable (intimacy) or unbearable (tension)
Dialogue Pacing
| Effect | Technique |
|---|---|
| Quick, natural exchange | Short lines alternating rapidly, no tags |
| Emotional weight | Long pause before a short reply |
| Avoidance | Answering a question with a question |
| Distance | Formal language between people who should be intimate |
| Intimacy | Silence, unfinished sentences, speaking at the same time |
Common Dialogue Pitfalls
| Pitfall | Why It Fails | Fix |
|---|---|---|
| On-the-nose | Characters say exactly what they feel | Add subtext, contradiction, or a deflection |
| Exposition dump | Characters explain the world to each other | Weave information into conflict or action |
| All characters sound the same | No distinct voice per character | Read dialogue aloud; if you can't tell who's speaking, rewrite |
| Perfect responses | Characters always know what to say | Let them be awkward, say the wrong thing, or say nothing |
| Over-explanation | Characters justify their own behavior | Trust the reader; show through action, not explanation |
6. Erotic Writing
The Purpose of Erotic Scenes in a VN
Erotic scenes are not separate from the story — they are the story at its most intense. They should:
- Advance the emotional arc — intimacy should change the relationship
- Reveal character — how a character behaves during sex tells us who they are
- Cost something — emotional or physical vulnerability is a risk
- Earn their place — if you can remove the sex scene and lose nothing, cut it
The Five-Stage Intimacy Model
| Stage | What Happens | Narrative Position | Emotional Function |
|---|---|---|---|
| 1. Attraction | Charged looks, accidental touches, awareness of each other's bodies. No explicit content. | Early story (first 20%) | Establishes that this relationship has a physical dimension |
| 2. Tension | Deliberate intimacy-building: sharing a bed, changing together, almost-kisses, confessions. Clothing stays on. | Mid-early (20–40%) | Builds anticipation; the gap between wanting and having |
| 3. Escalation | First kiss, hands under clothes, oral sex, manual stimulation. Partial nudity. | Mid-story (40–60%) | Crossing the physical threshold; the relationship changes |
| 4. Consummation | Full sexual intercourse. Multiple positions. Shared climax. Full nudity. | Late story (60–80%) | The physical culmination; vulnerability is at its peak |
| 5. Aftermath | Post-coital intimacy: conversation, silence, touch, sleep. Emotional vulnerability. | Climax / denouement (80–100%) | The emotional landing; this is what the reader remembers |
Erotic Writing Principles
-
Consent is explicit and character-appropriate. Every erotic scene requires a clear, unambiguous moment of consent. How consent happens depends on the character: a deredere gives enthusiastic verbal consent; a tsundere gives reluctant, conditional consent that must be checked; a kuudere gives consent through action and presence. Never leave consent ambiguous.
-
Character voice persists during sex. A tsundere does not become verbally effusive. A kuudere does not suddenly narrate her feelings. A deredere does not go silent. Intimacy reveals new facets — it does not erase the character.
-
Aftermath is mandatory. Never end a scene at climax. The emotional weight comes from what happens after: breathing, a touch, a word or silence that lands. The aftermath is where the reader processes what just happened.
-
Sensory specificity over euphemism. Use grounded, specific language:
Avoid Use Instead "his manhood" "the weight of him, the heat of his skin" "her womanly core" "her thighs parting, the wet warmth of her" "they made love" "she guided him inside — slowly, achingly slowly" "he pleasured her" "his mouth on her, her breath catching, her fingers in his hair" -
Pacing is controlled by the writing itself. Short, fragmented sentences for rapid escalation. Longer, sensory sentences for lingering. Paragraph breaks for breaths. White space is your pacing tool.
-
Eroticism is in the details, not the volume. A single specific detail — "the way she bit her lip" — is more erotic than a paragraph of generic description. Choose one sensory detail per moment.
-
The most erotic thing is emotional intimacy. A scene where characters finally admit they love each other during sex is more powerful than any physical description. The emotional stakes are what make the physical stakes matter.
Erotic Vocabulary
Use grounded sensory language. Design your project's lexical palette (the specific words it uses for bodies and acts) and use it consistently:
| Category | Vocabulary |
|---|---|
| Touch (hands) | fingertips, palm, trace, graze, press, grip, stroke, slide, cup, cradle, squeeze |
| Touch (body) | press against, arch into, shift beneath, wrap around, part for, buck against |
| Mouth | lips, tongue, breath, gasp, kiss, lick, nibble, suck, trace |
| Temperature | warm, hot, cool, chill, fever, flush, shiver, goosebumps |
| Sound | breath, gasp, whisper, moan, sigh, rustle, skin on skin, wet, rhythm, heartbeat |
| Sight | silhouette, shadow, glow, reflection, half-light, curve, line, arch, parting, glisten |
| Smell | skin, sweat, perfume, night air, incense, rain on hot ground |
| Emotion | ache, hunger, tenderness, fear, want, surrender, trust, vulnerability, release |
Content Standards
- Default to consensual, enthusiastic engagement for all erotic scenes
- The protagonist's pursuit of intimacy must always accept refusal gracefully
- Taboo and niche content (BDSM, power dynamics, specific kinks) should be telegraphed clearly so players can consent to engaging with it
- Non-consensual content requires explicit content warnings and player consent before the scene
7. Pacing
Micro-Pacing (Within a Scene)
Control the reader's rhythm through sentence and paragraph structure:
| Effect | Technique |
|---|---|
| Urgency / speed | Short sentences. Fragments. No paragraph breaks between actions. |
| Lingering / intimacy | Longer sentences. Multiple clauses. Sensory detail layered per paragraph. |
| Breath / pause | A single-sentence paragraph. White space. A line of dialogue alone. |
| Tension | Repetition of a short phrase. Shorter paragraphs as tension rises. |
| Release | A long paragraph after a series of short ones. A sigh in prose. |
Macro-Pacing (Across the Story)
- Alternate intense and quiet scenes. A confession of love should not be followed by another high-stakes scene. Give the reader space to feel it.
- Every erotic stage needs setup and cooldown. Attraction scenes spaced across multiple chapters. A consummation scene followed by a quiet aftermath chapter.
- Choices as pacing tools. A slower, more thoughtful choice (deciding between two people) should come after a fast, reactive choice (responding to a sudden event).
- Cliffhangers between chapters keep the player reading. The hook can be small — a character's expression, a half-heard phrase, a door closing.
8. Tone & Theme
Finding the Story's Tone
A VN's tone is the consistent emotional register of its narration, dialogue, and world. Define it early:
| Dimension | Question | Example: Light | Example: Heavy |
|---|---|---|---|
| Language | How ornate or plain is the prose? | Simple, conversational | Lyrical, metaphorical |
| Humor | How much? What kind? | Banter, situational | Sparse, dry, relief |
| World | How harsh or forgiving is the setting? | Welcoming, warm | Indifferent, cold |
| Eroticism | How explicit? How frequent? | Suggestive, occasional | Graphic, integral to plot |
| Stakes | What's the cost of failure? | Embarrassment | Heartbreak, loss |
Theme
A theme is not a message — it's a question the story explores. Good VN themes:
- Are personal — "What does it mean to trust someone?" not "What is the nature of trust?"
- Have no easy answer — both sides of the central conflict should have valid arguments
- Are embodied by the romance — each route explores a different answer to the same question
- Are tested by choices — the player's decisions should engage with the theme
Examples:
- "Is it better to love fully knowing it will end, or to protect yourself?"
- "What are you willing to give up to be truly seen by someone?"
- "Can you change who you are, or do you have to be accepted as you are?"
9. Workflow — From Concept to Artifact
This is the standard workflow for creating or expanding narrative content. Every step produces or updates artifacts.
Starting a New Project
- Define the high concept — logline, tone, content rating, estimated playtime, route count
- Create
docs/narrative/STORY.md— fill in the three-act structure, chapter outline, and first scene outlines - Create
docs/narrative/CHARACTER_DESIGN.md— prototype the protagonist and one romanceable character - Create
docs/narrative/WORLD_BUILDING.md— define the primary setting, its geography, rhythm, and atmosphere - Create
docs/narrative/ROUTES_AND_CHOICES.md— sketch the affinity system and first chapter's choices - Create
docs/narrative/EROTIC_CONTENT.md(if applicable) — define content boundaries and consent framework - Iterate — characters grow, world deepens, choices multiply. Keep artifacts updated.
Writing a New Chapter
- Read existing artifacts — review STORY.md (chapter arc), CHARACTER_DESIGN.md (character states), ROUTES_AND_CHOICES.md (affinity from previous chapter)
- Plan the chapter — emotional arc, central question, 2-4 choices, hook for next chapter
- Update STORY.md — add scene outlines, set status to
[ ] Outline - Update ROUTES_AND_CHOICES.md — add choices to the choice catalog, plan affinity shifts
- Write the chapter — scene by scene, following the structure defined in Section 1
- Update artifacts — mark scenes
[x] Written, update affinity maps, add change log entries - Validate — run the validation checklist (Section 10)
Adding a New Character
- Define their archetype — use Section 3 (Character Design) to build their profile
- Update CHARACTER_DESIGN.md — full profile: identity, personality, arc, intimacy style, relationships
- Update STORY.md — add their scenes to the outline
- Update ROUTES_AND_CHOICES.md — add affinity variable, choices that involve them
- Update WORLD_BUILDING.md — add any locations tied to this character
- Update EROTIC_CONTENT.md (if applicable) — plan their intimacy stages
Writing an Erotic Scene
- Check the five-stage model — verify this scene's position in the intimacy arc (EROTIC_CONTENT.md)
- Read existing intimacy — ensure continuity of character voice and physical progression
- Write the scene — consent cue → build tension → explicit content → aftermath (mandatory)
- Update EROTIC_CONTENT.md — mark the scene complete, add content notes
- Update STORY.md — mark scene status
[x] Written - Validate — run the erotic content validation checklist (Section 10)
10. Validation Checklist
Before finalizing any narrative content:
Story Structure
- Story follows a clear three-act shape
- Each chapter has an emotional arc and a central question
- Choices have meaningful, trackable consequences
- Branching density matches the project's scope
- Each route feels distinct from the others
Character
- Every character has a distinct voice (read dialogue aloud to test)
- Romanceable characters have a core identity, a backbone, a voice, an arc, and an intimacy style
- The protagonist has enough personality to be interesting but room for player projection
- Supporting characters have one clear function and one memorable trait
Dialogue
- No two characters sound the same
- Subtext replaces on-the-nose emotional statements
- Exposition is woven into conflict or action
- Silence and pauses are used deliberately
- Dialogue compresses real speech without losing naturalism
Erotic Content (if applicable)
- Position in the five-stage intimacy model is appropriate for the story's progression
- Consent is explicit and character-appropriate
- Aftermath is present (never end at climax)
- Character voice is maintained during sex
- Sensory, specific language — no purple prose or coy euphemisms
- The erotic scene advances the emotional arc or reveals character
Worldbuilding
- The world is defined by geography, rhythm, and rules
- Atmosphere is built through recurring sensory motifs
- World details are shown through action, not exposition
- The setting reflects or contrasts the emotional tone of scenes
Pacing
- Intense and quiet scenes alternate at every level
- Erotic scenes have setup and cooldown
- Choices arrive at meaningful intervals (not too dense, not too sparse)
- Each chapter ends with a hook for the next
Artifacts
- STORY.md exists and reflects the current story state
- CHARACTER_DESIGN.md exists with profiles for all active characters
- WORLD_BUILDING.md exists with geography, rhythm, rules, and sensory motifs
- ROUTES_AND_CHOICES.md exists with affinity map, branching map, and choice catalog
- EROTIC_CONTENT.md exists (if project has explicit content)
- Change logs are up to date in all artifacts
- Completed scenes are marked
[x]in checklists