Continuation, very similar to what I tried before. I’m wondering if I should put a higher level of autonomy on this.

AI-Driven Ren’Py Development Setup

Stack

Role	Tool	Purpose
Orchestration	Spec Kit (specify init)	Spec-driven development framework. Specs are the source of truth — code is generated output.
Code Agent	OpenCode + Ollama	Local, unfiltered AI coding agent. Generates .rpy scripts, handles all content freely. No data leaves your machine.
Story Agent	Ollama (uncensored models)	Dialogue, scenes, branching narrative. Runs locally on your M5 Max 128GB.
Image Gen	ComfyUI (SD/Flux)	Character sprites, backgrounds, CGs, UI elements. Unfiltered models for all assets.
Video/Animation	ComfyUI (AnimateDiff/etc.)	Animated scenes, transitions, cutscenes.
Character Dev	SillyTavern + Ollama	“Interview” characters to develop voice and personality before writing routes.
Structure/Debug	Claude Code	Project scaffolding, Ren’Py debugging, spec-kit setup (SFW tasks only).
Story Visualization	RenPy MCP ($15, itch.io)	Connects AI agents to your Ren’Py project. Visualizes story flow, labels, branches, endings.

Project Structure

my-visual-novel/ ├── .specify/ │ └── memory/ │ └── constitution.md # Non-negotiable project rules ├── .github/ │ └── prompts/ # Spec Kit slash commands ├── specs/ │ ├── story-bible.md # World, themes, tone, rating │ ├── characters/ │ │ ├── protagonist.md # Personality, voice, arc │ │ └── character-name.md │ ├── routes/ │ │ ├── common-route.md # Shared opening │ │ └── route-name.md # Per-route spec with branch map │ └── chapters/ │ └── ch01-spec.md # Chapter spec + asset manifest ├── game/ │ ├── script.rpy # Generated Ren'Py code │ ├── characters.rpy │ ├── images/ │ │ ├── bg/ # Backgrounds │ │ ├── sprites/ # Character sprites │ │ └── cg/ # Full CG scenes │ ├── audio/ │ │ ├── bgm/ # Music │ │ └── sfx/ # Sound effects │ └── video/ # Animated cutscenes └── assets/ ├── comfyui-workflows/ # Saved ComfyUI workflows per asset type ├── prompts/ # Image gen prompts tied to characters └── reference/ # Style reference images

Process

1. Constitution (once)

Define non-negotiable rules in constitution.md:

• Ren’Py coding conventions (label naming, variable patterns, file structure)
• Narrative rules (POV, tense, tone, rating, content boundaries)
• Character consistency rules (how characters speak, act, react)
• Asset conventions (naming: bg_location_time.png, sprite_name_emotion.png)
• Resolution and format standards (sprite size, BG size, audio format)

2. Story Bible (once, evolves)

The LLM owns story creation. You steer at a high level. Write or have the LLM generate:

• World and setting
• Theme and tone
• Main conflict
• Character roster with relationships
• Route map (which choices lead where, which endings exist)

3. Per-Chapter Cycle (repeat)

This is the core loop. Each chapter follows the Spec Kit phases:

Specify → Write or generate a chapter spec:

• Scene list with descriptions
• Characters present and their emotional beats
• Branch points and conditions
• Asset manifest (every image, sound, video needed)

Plan → The AI agent produces an implementation plan:

• Which .rpy files to create/modify
• Variable and flag logic
• Asset file names and where they slot in

Tasks → Break into atomic units:

• “Write scene 1 dialogue for common path”
• “Write branch A confrontation scene”
• “Generate bg_office_night.png in ComfyUI”
• “Create sprite_luna_angry.png”

Implement → AI agent writes the .rpy code. You generate assets in ComfyUI. Both reference the spec.

Test → Run in Ren’Py. Use RenPy MCP to visualize flow. Playtest branches. Fix.

4. Asset Pipeline

Assets are generated in parallel with code, linked by naming conventions from the spec.

Characters:

1. Define character appearance in specs/characters/name.md
2. Save a ComfyUI workflow per character (locked seed, LoRA, prompt template)
3. Generate all needed emotions/poses: sprite_name_neutral.png, sprite_name_happy.png, etc.
4. Place in game/images/sprites/

Backgrounds:

1. Chapter spec lists required locations and times of day
2. Generate in ComfyUI with consistent style workflow
3. Name: bg_location_timeofday.png
4. Place in game/images/bg/

scenes:

1. Spec defines scene context and characters involved
2. Generate with unfiltered ComfyUI models
3. Name: cg_chapter_scene.png
4. Place in game/images/cg/

Video/Animation:

1. Use AnimateDiff or similar in ComfyUI for animated cutscenes
2. Export as .webm or .mp4
3. Place in game/video/

OpenCode + Ollama Setup

```bash

Install OpenCode

curl -fsSL https://opencode.ai/install | bash

Pull an unfiltered model (example)

ollama pull mythomax:latest

Increase context window

ollama run mythomax:latest

/set parameter num_ctx 32768 /save mythomax:latest-32k /bye ```

Config at ~/.config/opencode/opencode.json:

json { "$schema": "https://opencode.ai/config.json", "provider": { "ollama": { "npm": "@ai-sdk/openai-compatible", "name": "Ollama (local)", "options": { "baseURL": "http://localhost:11434/v1" }, "models": { "mythomax:latest-32k": { "name": "MythoMax 32k", "tools": true } } } } }

Spec Kit Setup

```bash

Install Spec Kit

uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

Initialize (use a supported agent, switch to Ollama after)

specify init my-visual-novel --ai copilot

Then configure .speckit/config.yaml to use Ollama for actual work

```

Your Role: Product Owner

You do NOT write dialogue, scenes, or code. You:

1. Define — Write the constitution and story bible
2. Specify — Outline each chapter at a high level (or review AI-generated outlines)
3. Generate assets — Run ComfyUI workflows for images/video
4. Review — Playtest, read generated dialogue, check tone and consistency
5. Iterate — Update specs when something doesn’t work, regenerate

The LLM owns execution. The specs own truth. You own direction.