claude-code-arcane 1.0.0

package/skills/vn-comfyui-gen/references/comfyui-vn-workflows.md

@@ -0,0 +1,197 @@
+# ComfyUI Workflows for Visual Novel Assets
+
+## Overview
+
+This document describes the recommended ComfyUI workflow strategies for
+generating visual novel assets with consistency and production quality.
+
+## Prerequisites
+
+### Required Custom Nodes
+| Node Pack | Purpose | Install |
+|-----------|---------|---------|
+| ComfyUI-Manager | Node management | Pre-installed in most setups |
+| ComfyUI-Impact-Pack | Face detection, inpainting | `git clone` in custom_nodes/ |
+| ComfyUI-IPAdapter-plus | Character consistency | `git clone` in custom_nodes/ |
+| comfyui_controlnet_aux | ControlNet preprocessors | `git clone` in custom_nodes/ |
+| ComfyUI-LayerDiffuse | Transparent backgrounds | `git clone` in custom_nodes/ |
+| ComfyUI-KJNodes | Utility nodes | `git clone` in custom_nodes/ |
+
+### Recommended Models by Style
+
+#### Anime / Classic VN
+- **Checkpoint**: Anything V5 / AOM3A3 / Counterfeit V3
+- **VAE**: kl-f8-anime2 or built-in
+- **LoRA**: flat-color-anime, visual-novel-style
+- **ControlNet**: control_v11p_sd15_openpose, control_v11p_sd15_lineart
+
+#### Semi-Realistic
+- **Checkpoint**: Juggernaut XL / RealVis XL 4.0
+- **VAE**: sdxl_vae
+- **LoRA**: detail-enhancer, skin-texture
+- **ControlNet**: control_lora_rank128_v11p_sd15_openpose
+
+#### Stylized / Painterly
+- **Checkpoint**: DreamShaper XL / Pony Diffusion V6
+- **VAE**: sdxl_vae
+- **LoRA**: watercolor-style, cel-shading
+
+---
+
+## Workflow 1: Character Sprite (Base)
+
+### Goal
+Generate a front-facing character sprite with transparent background.
+
+### Node Flow
+```
+[Checkpoint Loader] → [CLIP Text Encode (Positive)]
+                    → [CLIP Text Encode (Negative)]
+                    → [KSampler]
+                    → [LayerDiffuse Decode] → [Save Image (PNG)]
+                    
+[Empty Latent Image (768x1344)] → [KSampler]
+[ControlNet (OpenPose)] → [KSampler]  # For pose control
+```
+
+### Settings
+- **Steps**: 30-40
+- **CFG**: 7-9
+- **Sampler**: DPM++ 2M Karras
+- **Scheduler**: Karras
+- **Resolution**: 768x1344 (SD1.5) or 1024x1792 (SDXL)
+- **Denoising**: 1.0 (full generation)
+
+### Prompt Template
+```
+Positive: masterpiece, best quality, [art_style], 1girl/1boy,
+[character_description], [outfit_description], [hair], [eyes],
+standing, front view, full body, arms at sides, looking at viewer,
+simple pose, clean lines, visual novel character sprite
+
+Negative: multiple people, background, scenery, watermark, text,
+extra fingers, extra limbs, deformed, blurry, low quality, worst quality,
+chibi, partial body, cropped, from behind, from side
+```
+
+---
+
+## Workflow 2: Expression Swap (Inpainting)
+
+### Goal
+Change facial expression while keeping body identical.
+
+### Node Flow
+```
+[Load Base Image] → [Create Face Mask (Impact Pack)] 
+                  → [Set Latent Noise Mask]
+                  → [KSampler (Inpaint)] 
+                  → [Composite Original + Inpainted]
+                  → [Save Image]
+
+[IP-Adapter (base image as reference)] → [KSampler]
+```
+
+### Settings
+- **Denoising**: 0.55-0.70 (enough to change expression, not identity)
+- **Mask padding**: 30-50px around face
+- **Steps**: 25-30
+- **CFG**: 6-8 (lower for subtlety)
+
+### Per-Expression Prompt Additions
+| Expression | Add to Positive | Add to Negative |
+|-----------|----------------|-----------------|
+| happy | smiling, bright eyes, open mouth smile | sad, angry, crying |
+| sad | downcast eyes, slight frown, melancholy | smiling, happy, laughing |
+| angry | furrowed brows, intense eyes, tight mouth | smiling, relaxed, happy |
+| surprised | wide eyes, raised eyebrows, open mouth | calm, relaxed, neutral |
+| embarrassed | blushing, looking away, shy smile | confident, bold, direct |
+| crying | tears, distressed, trembling lips | happy, smiling, calm |
+
+---
+
+## Workflow 3: Background Scene
+
+### Goal
+Generate consistent environment backgrounds at game resolution.
+
+### Node Flow
+```
+[Checkpoint Loader] → [CLIP Text Encode]
+                    → [KSampler]
+                    → [Upscale (2x)]
+                    → [Downscale to target resolution]
+                    → [Save Image]
+```
+
+### Settings
+- **Resolution**: 1920x1080 (or generate at 960x540 and upscale 2x)
+- **Steps**: 35-50 (backgrounds benefit from more steps)
+- **CFG**: 8-12
+- **Denoising**: 1.0
+
+### Time-of-Day Variants
+Use img2img with the day version as base:
+- **Sunset**: denoising 0.35, add "golden hour, warm lighting, orange sky"
+- **Night**: denoising 0.40, add "nighttime, moonlight, dark sky, artificial lighting"
+- **Rain**: denoising 0.30, add "rainy, wet surfaces, overcast, puddles"
+
+---
+
+## Workflow 4: CG Event Illustration
+
+### Goal
+Generate dramatic event illustrations with known characters.
+
+### Node Flow
+```
+[Checkpoint Loader] → [CLIP Text Encode]
+                    → [KSampler]
+                    → [IP-Adapter (character refs)]
+                    → [ControlNet (composition pose)]
+                    → [Upscale + Detail Enhancement]
+                    → [Save Image]
+```
+
+### Settings
+- **Resolution**: 1920x1080 (landscape event) or 1080x1920 (portrait closeup)
+- **Steps**: 40-60 (quality matters for CGs)
+- **CFG**: 7-10
+- **IP-Adapter weight**: 0.6-0.8 (balance identity vs scene freedom)
+
+---
+
+## Workflow 5: UI Elements
+
+### Goal
+Generate themed UI components (textbox, buttons, frames).
+
+### Approach
+- Use inpainting or img2img from a base layout
+- Generate decorative elements separately and composite
+- For semi-transparent elements: generate opaque, then adjust alpha in post
+
+### Common UI Prompts
+```
+Textbox: ornate frame border, decorative, [style] aesthetic,
+semi-transparent, dark background, golden trim, visual novel textbox,
+UI element, isolated on black
+
+Button: rounded rectangle, [style] button, normal state,
+clean edges, readable text area, UI element
+
+Menu BG: [atmosphere] scene, blurred, bokeh, visual novel menu background,
+no characters, atmospheric, cinematic
+```
+
+---
+
+## Tips for Consistency
+
+1. **Save seeds**: record the seed for every approved generation
+2. **IP-Adapter is key**: always reference the approved base character image
+3. **Batch with same settings**: generate all expressions in one session
+4. **ControlNet for poses**: use the same pose reference for all characters
+5. **Color grading**: apply the same color adjustment to all assets in a batch
+6. **Resolution consistency**: always generate at the same base resolution
+7. **Style LoRA**: use the same style LoRA at the same weight for all assets

package/skills/vn-dialogue-tree/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: vn-dialogue-tree
+description: "Design and visualize branching dialogue trees with conditions, flags, and affinity tracking. Produces Mermaid flowcharts and Ren'Py-ready choice structures."
+category: "visualnovel"
+argument-hint: "[chapter:<name> | route:<name> | scene:<name>]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion
+---
+
+When this skill is invoked:
+
+1. **Parse target** — chapter, route, or scene to map
+2. **Load narrative context**:
+   - Read `design/narrative/story-outline.md` — fail if missing:
+     > "No story outline found. Run `/vn-narrative-design` first."
+   - Read `game/variables.rpy` if exists — current flag/variable state
+   - Read target chapter .rpy if editing existing
+
+---
+
+## Phase 1: Identify Choice Points
+
+For the target scope, list every decision point:
+
+| # | Location | Choice Text | Type | Variables Affected |
+|---|----------|-------------|------|-------------------|
+| 1 | ch3_scene2 | "Confess feelings" / "Stay silent" | Affinity | sakura_affinity +10/-0 |
+| 2 | ch3_scene4 | "Investigate alone" / "Ask for help" | Flag | flag_solo_investigation |
+| 3 | ch4_scene1 | [auto: courage >= 30] | Stat check | — (gate only) |
+
+---
+
+## Phase 2: Build Flow Diagram
+
+Generate a Mermaid flowchart for the branching structure:
+
+```mermaid
+flowchart TD
+    START[Chapter 3 Start] --> S1[Scene 1: School morning]
+    S1 --> S2[Scene 2: Rooftop conversation]
+    S2 --> C1{Choice: Confess?}
+    C1 -->|Confess| S3A[Scene 3A: Confession reaction]
+    C1 -->|Stay silent| S3B[Scene 3B: Awkward silence]
+    S3A --> S4[Scene 4: After school]
+    S3B --> S4
+    S4 --> C2{Choice: Investigate?}
+    C2 -->|Alone| S5A[Scene 5A: Solo investigation]
+    C2 -->|Ask help| S5B[Scene 5B: Team investigation]
+    S5A --> GATE{courage >= 30?}
+    GATE -->|Yes| S6A[Secret discovery]
+    GATE -->|No| S6B[Dead end — retry hint]
+    S5B --> S6C[Shared discovery]
+    S6A --> MERGE[Chapter 3 End]
+    S6B --> MERGE
+    S6C --> MERGE
+```
+
+Write the diagram to `design/narrative/trees/[target]-flow.md`.
+
+---
+
+## Phase 3: Condition Matrix
+
+Build a truth table showing how flag combinations affect outcomes:
+
+| confessed | solo_investigate | courage>=30 | Outcome |
+|-----------|-----------------|-------------|---------|
+| true | true | true | Secret + romantic scene in ch5 |
+| true | true | false | Dead end retry, romantic undertone |
+| true | false | — | Team path + romantic subplot |
+| false | true | true | Secret discovery, friendship path |
+| false | true | false | Dead end retry, neutral |
+| false | false | — | Team path, friendship route |
+
+**Total unique paths through this chapter**: [count]
+**Variables introduced**: [list new flags/vars]
+**Variables consumed**: [list flags checked from previous chapters]
+
+---
+
+## Phase 4: Validate Connectivity
+
+Check for:
+- **Dead ends**: paths that don't connect to any label/jump target
+- **Unreachable nodes**: labels that no path can reach
+- **Orphaned flags**: flags set but never checked (or checked but never set)
+- **Infinite loops**: circular jump chains
+- **Missing converge points**: branches that never rejoin
+
+Report issues:
+> ⚠ Flag `solo_investigate` is set in ch3 but never checked in ch4-ch8
+> ⚠ Label `chapter_3_secret_path` is unreachable (requires courage >= 30 but
+>   courage max at this point is 25)
+
+---
+
+## Phase 5: Generate Ren'Py Skeleton
+
+From the validated tree, generate the `.rpy` choice structure:
+
+```renpy
+label chapter_3_scene_2:
+    menu:
+        narrator "What should I do?"
+        "Confess my feelings to [char].":
+            $ sakura_affinity += 10
+            $ flags.confessed_ch3 = True
+            jump chapter_3_confess_path
+        "Stay silent for now.":
+            $ flags.confessed_ch3 = False
+            jump chapter_3_silent_path
+```
+
+Write skeleton to `game/chapters/[target]_skeleton.rpy` — this is a scaffold
+for `/vn-script` to fill with actual dialogue.
+
+---
+
+## Phase 6: Output Files
+
+1. `design/narrative/trees/[target]-flow.md` — Mermaid diagram
+2. `design/narrative/trees/[target]-conditions.md` — condition matrix
+3. `game/chapters/[target]_skeleton.rpy` — Ren'Py choice skeleton (if approved)
+4. Update `game/variables.rpy` with any new flags/variables introduced
+
+Suggest next: `/vn-script chapter:[target]` to fill in dialogue

package/skills/vn-gdd/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: vn-gdd
+description: "Create a Visual Novel Game Design Document: concept, target audience, narrative structure, game systems, art direction, audio design, technical spec, and production plan."
+category: "visualnovel"
+argument-hint: "[project-name or empty]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write, Edit, WebSearch, AskUserQuestion
+---
+
+When this skill is invoked:
+
+1. **Check for existing work**:
+   - Read `design/gdd/game-concept.md` — use if exists
+   - Read `design/narrative/story-outline.md` — pull narrative data
+   - Read `design/art/art-bible.md` — pull art direction
+   - Read `design/characters/*.md` — pull character data
+
+2. Use **incremental file writing**: create skeleton immediately, fill section by section.
+
+---
+
+## VN-GDD Structure
+
+Write to `design/gdd/visual-novel-gdd.md`:
+
+### Section 1: Game Overview
+- **Title**: Working title
+- **Logline**: One-sentence pitch (under 25 words)
+- **Genre**: Primary + subgenres (e.g., Romance / Mystery / School Life)
+- **Platform**: PC, Web, Mobile, Console
+- **Engine**: Ren'Py [version]
+- **Target playtime**: [hours] per route, [hours] total with all routes
+- **Content rating**: target ESRB/PEGI rating and why
+- **Unique selling point**: what makes this VN stand out
+
+### Section 2: Target Audience
+- **Primary audience**: age range, gender distribution, VN experience level
+- **Player motivations**: story immersion, romance, mystery solving, collection
+- **Comparable titles**: 3-5 reference VNs with what's borrowed from each
+- **Market positioning**: where this sits relative to comparables
+
+### Section 3: Narrative Design
+- **Story brief**: [from story outline]
+- **Theme statement**: core theme in one sentence
+- **Act structure**: high-level act breakdown
+- **Route map**: diagram of all routes and endings
+- **Total word count estimate**: [scope × ~200 words/minute × playtime]
+- **Choice count**: total meaningful choices across all routes
+- **Ending count**: all endings by type (good/normal/bad/secret)
+
+### Section 4: Character Design
+- **Cast size**: protagonist + [N] major + [N] minor characters
+- **Character summary table**: name, role, archetype, route (if applicable)
+- **Relationship dynamics**: key tensions and alliances
+- **Character arc summaries**: 2-3 sentences per major character
+
+### Section 5: Game Systems
+Visual novels may include gameplay systems beyond choices:
+
+| System | Description | Complexity |
+|--------|-------------|-----------|
+| **Affinity tracking** | Relationship points per character | Core |
+| **Flag system** | Boolean story progression flags | Core |
+| **Route locking** | Conditions to enter each route | Core |
+| **Gallery/CG unlock** | Collectible CG viewer | Standard |
+| **Ending tracker** | Track which endings have been seen | Standard |
+| **Stat system** | Player stats (courage, intelligence, etc.) | Optional |
+| **Inventory** | Items that affect dialogue/choices | Optional |
+| **Mini-games** | Embedded gameplay segments | Optional |
+| **Timed choices** | Time-limited decisions | Optional |
+| **Relationship map** | Visual relationship tracker | Optional |
+
+For each included system, document:
+1. **Purpose** — why this system exists (player experience it creates)
+2. **Mechanics** — how it works (formulas, thresholds, conditions)
+3. **UI representation** — how the player sees/interacts with it
+4. **Edge cases** — unusual situations and how they're handled
+
+### Section 6: Art Direction
+- **Visual style**: anime / semi-realistic / stylized / pixel art
+- **Color palette**: primary, secondary, accent + emotional associations
+- **Character sprites**: count, expressions per character, outfit variants
+- **Backgrounds**: count, time variants (day/night)
+- **CG illustrations**: count, key events they depict
+- **UI style**: textbox design, menu aesthetic
+- **Reference board**: list of visual references
+
+### Section 7: Audio Design
+- **BGM tracks**: count, genres, mood mapping to scenes
+- **SFX**: ambient sounds, UI sounds, impact sounds
+- **Voice acting**: full / partial / none — if partial, which scenes
+- **Audio adaptive behavior**: music changes based on affinity or route
+
+### Section 8: Technical Specification
+- **Engine**: Ren'Py [version]
+- **Target resolution**: [width × height]
+- **File structure**: project directory layout
+- **Save system**: auto-save points, manual save slots count
+- **Localization**: supported languages, translation system
+- **Accessibility**: font options, text speed, skip modes, colorblind support
+- **Build targets**: platforms and distribution (Steam, itch.io, web)
+- **Performance targets**: load times, transition smoothness
+
+### Section 9: Production Plan
+- **Milestone breakdown**:
+  1. Pre-production: story outline, character designs, art bible
+  2. Production: script writing, asset generation, implementation
+  3. Alpha: all routes playable, placeholder assets acceptable
+  4. Beta: all assets final, full QA pass
+  5. Release: polished, tested, distributed
+
+- **Asset production estimates**:
+  | Asset Type | Count | Est. Time |
+  |-----------|-------|-----------|
+  | Character sprites | [N chars × M expressions] | |
+  | Backgrounds | [N locations × M variants] | |
+  | CG illustrations | [N events] | |
+  | BGM tracks | [N] | |
+  | Script writing | [N words] | |
+  | Ren'Py implementation | [N chapters] | |
+
+### Section 10: Acceptance Criteria
+Testable conditions for project completion:
+- [ ] All routes playable from start to each ending
+- [ ] All choices lead to valid paths (no dead ends)
+- [ ] All character sprites display correctly with all expressions
+- [ ] All backgrounds load at target resolution
+- [ ] All CG events trigger at correct story points
+- [ ] Gallery tracks all unlockable CGs
+- [ ] Save/load works across all story points
+- [ ] Settings persist between sessions
+- [ ] Build runs on all target platforms
+- [ ] Localization complete for all target languages

package/skills/vn-narrative-design/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: vn-narrative-design
+description: "Design the complete narrative structure for a visual novel: story arcs, branching paths, endings, character relationships, and pacing. Produces a story outline document that drives all other VN skills."
+category: "visualnovel"
+argument-hint: "[concept-hint or empty] [--scope short|medium|epic]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write, Edit, WebSearch, AskUserQuestion
+---
+
+When this skill is invoked:
+
+1. **Parse arguments** for concept hint and scope
+   - `short`: 2-5 hours playtime, 1-3 endings, linear with minor branches
+   - `medium`: 5-15 hours, 3-6 endings, moderate branching (default)
+   - `epic`: 15+ hours, 6+ endings, complex branching with routes
+
+2. **Check for existing work**:
+   - Read `design/narrative/story-outline.md` if it exists (resume)
+   - Read `design/gdd/game-concept.md` if it exists (use pillars)
+   - Read `design/characters/*.md` for established characters
+
+---
+
+## Phase 1: Story Foundation
+
+Ask the user interactively using `AskUserQuestion`:
+
+**Tab "Genre"**: What genre defines your visual novel?
+- Romance / Drama / Mystery-Thriller / Fantasy-Adventure / Horror / Sci-Fi
+
+**Tab "Tone"**: What overall tone should the story have?
+- Lighthearted & Comedic / Emotional & Dramatic / Dark & Suspenseful / Bittersweet & Reflective
+
+**Tab "POV"**: What point of view for the protagonist?
+- Named protagonist with defined personality
+- Self-insert protagonist (player IS the character)
+- Multiple viewpoint characters
+
+Then ask in conversation (not constrained choices):
+- What emotional experience should the player have by the end?
+- Are there themes you want to explore?
+- Any reference visual novels or stories that inspire this project?
+
+**Synthesize** into a **Story Brief**:
+> **Genre**: [genre] | **Tone**: [tone] | **POV**: [pov]
+> **Core theme**: [theme]
+> **Emotional arc**: [start feeling] → [midpoint shift] → [end feeling]
+> **Inspirations**: [references]
+
+---
+
+## Phase 2: Story Structure Design
+
+### Act Structure
+Design a 3-5 act structure appropriate to scope:
+
+| Act | Purpose | Chapters | Key Events |
+|-----|---------|----------|------------|
+| I — Setup | Introduce world, characters, conflict | 1-3 | Inciting incident |
+| II — Rising | Deepen relationships, escalate conflict | 4-8 | Major choice points |
+| III — Climax | Confrontation, route-specific peaks | 9-11 | Route climaxes |
+| IV — Resolution | Endings, epilogues | 12+ | Multiple endings |
+
+### Route Architecture (for medium/epic scope)
+Design the branching structure:
+
+```
+Common Route (Acts I-II early)
+├── Route A: [Character/Theme]
+│   ├── Good Ending A1
+│   ├── Normal Ending A2
+│   └── Bad Ending A3
+├── Route B: [Character/Theme]
+│   ├── Good Ending B1
+│   └── Bad Ending B2
+├── Route C: [Character/Theme] (unlockable after A+B)
+│   └── True Ending
+└── Hidden Route (conditions: all good endings seen)
+    └── Secret Ending
+```
+
+### Branching Philosophy
+Present options and let user choose:
+- **Hub-and-spoke**: common trunk with route branches (Fate/stay night style)
+- **Waterfall**: early choices create increasingly divergent paths (428 style)
+- **Parallel routes**: independent character routes selected early (Clannad style)
+- **Kinetic with choices**: mostly linear with impactful decision points
+
+---
+
+## Phase 3: Character Web
+
+For each major character, define:
+
+| Field | Description |
+|-------|-------------|
+| **Name** | Full name + nickname/alias |
+| **Role** | Protagonist / Love Interest / Antagonist / Support / Mentor |
+| **Archetype** | (e.g., Tsundere, Genki, Kuudere, Mentor, Trickster) |
+| **Want** | External goal (what they pursue) |
+| **Need** | Internal growth (what they actually need) |
+| **Secret** | Hidden information revealed during their route |
+| **Relationship to MC** | Initial dynamic and how it evolves |
+| **Conflict** | What creates tension with the protagonist |
+| **Key scenes** | 3-5 pivotal moments in their arc |
+
+Design the **Relationship Map** — how characters relate to each other beyond
+just their connection to the protagonist.
+
+---
+
+## Phase 4: Pacing and Choice Architecture
+
+### Choice Design Principles
+- **Meaningful choices**: every choice should affect at least one variable
+  (affinity, flag, stat) — no dead-end cosmetic choices
+- **Foreshadowing**: good choices hint at consequences without spoiling
+- **Characterization**: choices reveal the protagonist's personality
+- **Tension pacing**: alternate high-tension choices with breathing room
+
+### Choice Types:
+1. **Affinity choices** — increase relationship with a character (+5, +10)
+2. **Route locks** — accumulate to determine which route you enter
+3. **Flag choices** — set boolean flags that alter future scenes
+4. **Stat checks** — gated by accumulated stats (courage, intelligence)
+5. **Timed choices** — pressure decisions (optional, use sparingly)
+
+### Pacing Template per Chapter:
+```
+Scene 1: Establishing (calm) — set the scene, re-orient player
+Scene 2: Development (rising) — advance plot or relationship
+Scene 3: Choice point (peak) — meaningful decision
+Scene 4: Consequence (falling) — show impact of choice
+Scene 5: Hook (cliffhanger) — motivate next chapter
+```
+
+---
+
+## Phase 5: Endings Design
+
+For each ending, define:
+- **Trigger conditions**: flags, affinity thresholds, choices required
+- **Emotional tone**: triumphant / bittersweet / tragic / ambiguous
+- **Resolution**: what the ending resolves (and what it leaves open)
+- **Epilogue**: what happens after the main conflict resolves
+- **Unlock order**: which endings should be experienced first for maximum impact
+
+---
+
+## Phase 6: Write Story Outline Document
+
+Write to `design/narrative/story-outline.md` using incremental file writing:
+
+```markdown
+# [Title] — Story Outline
+
+## Story Brief
+[from Phase 1]
+
+## Act Structure
+[from Phase 2]
+
+## Route Map
+[branching diagram from Phase 2]
+
+## Character Web
+[from Phase 3]
+
+## Choice Architecture
+[from Phase 4 — list every major choice point with chapter, type, and impact]
+
+## Endings
+[from Phase 5]
+
+## Chapter Breakdown
+[per-chapter: scenes, characters present, choices, flags set/checked]
+
+## Asset Requirements
+[scenes → backgrounds needed, characters → sprites needed, CGs → event art needed]
+```
+
+After completion, suggest next steps:
+- `/vn-character-design` for detailed character profiles and sprite specs
+- `/vn-gdd` for the full game design document
+- `/vn-dialogue-tree` for detailed choice flowcharts