NovelToGame

Turn a novel in any language into a source-grounded, fully playable game.

NovelToGame is an open-source Agent Skills toolkit for Claude Code, Codex, and Kimi Code. It turns novel adaptation into a staged workflow: source analysis, concept selection, world and art direction, implementation, and runtime QA.

Bring a novel in any language and choose the target runtime. Generated artifacts follow the requested language; build and QA stay on the chosen platform instead of silently falling back to an easier substitute.

中文 · Play Online · Quick Start · Workflow · Skills · Artifacts · Contributing

Play Online

Three playable adaptations, each available in a browser right now and linked to the case study behind it: source provenance, concept trade-offs, game and art direction, runnable source, and evidence from the playable paths.

Journey to the West · Three Borrowings of the Banana Fan

One wave of a fan blew you fifty thousand li. Take the mountain back one turn at a time.

Command Wukong's party through the three borrowings of the Banana-Leaf Fan: read the five-element wheel, set a formation, transform your way in where force will not work, and turn a demon king who outclasses you into a rainstorm over the Mountain of Flames.

Play in browser · Read the case study · design estimate: 45–90 min · all ages · playable prototype

Jin Ping Mei · Ledger of Desire

Choose whose door you enter tonight. Find out whose door knocks in the morning.

Six nights, three courtyards. Spend each day converting silver, standing and secrets into the right to choose — then wake up and settle what the other two are owed.

Play in browser · Read the case study · design estimate: 20–30 min · 18+ · playable prototype

Project Plateau · The Lost World · 3D

A real-time first-person 3D field-photography game adapted from Arthur Conan Doyle's The Lost World. Cross a connected plateau, observe a living Iguanodon family, expose four glass plates under aerial pressure, and return with the views that survived.

Play the full expedition on desktop, or watch the 15-second gameplay preview on other devices.

https://github.com/user-attachments/assets/27819247-4e4d-4bf0-8f0f-43d4125c4d45

Play in your browser — no install · Read the case study · Share feedback · 1–3 min run · desktop WebGL2 · playable prototype

Why NovelToGame

A one-line “turn this book into a game” prompt often produces a generic reskin or a clickable plot summary. NovelToGame keeps the adaptation traceable and gives each major decision a clear owner:

• Source-grounded adaptation: extract rules, spaces, character agency, conflicts, and visual anchors with citations;
• Real game design: turn source evidence into player verbs, systems, levels, feedback, failure, and outcomes;
• Target-runtime delivery: build for the approved platform or engine without implementation silently redesigning the game;
• Optional, restrained voice: synthesize only selected high-value lines at build time, keep subtitles and mute fallbacks, and never send the whole novel to a TTS provider by default;
• Evidence-based QA: verify startup, rendering, input, the core loop, an outcome, restart, and explicit limitations in the tested runtime.

Quick Start

1. Install the seven skills

Install adapters for all three CLIs on the same machine:

npx skills add worldwonderer/novel-to-game -g -y -s '*' \
  -a claude-code -a codex -a kimi-code-cli

Cloning the repository also enables project-local skill discovery in all three CLIs.

2. Start an adaptation

Give the agent a novel file, directory, or link:

Use novel-to-game quick to adapt this novel into a fully playable game.
Recommend the target platform, genre, and engine from the source, and keep the first build to about 15 minutes.
Let the player enter the world as an original character with a new playable route through its conflict.

When you want an interactive story rather than a systems game, say so. That locks the narrative-led experience profile, so concept, design, and QA judge continuous scenes, character dialogue, testimony, and key choices instead of applying rounds, cards, and resource bars:

Use novel-to-game quick to adapt this novel into an interactive story.
Carry the experience with continuous scenes, character dialogue, testimony, and key choices.
Keep variables as hidden causal tags rather than a visible stat panel.
Key choices must change later scenes, character attitudes, and the ending, and be named back in later text.

The narrative track lowers no standard: it still needs a recognizable gameplay precedent, the same three-phase arc, and the same hard vetoes. Only the expression changes -- new people to question, new ways to press a contradiction, and attitudes that shifted because of what you did earlier.

quick is the low-friction option: the agent drafts sensible defaults, asks only about materially branching or safety-sensitive choices, compares three concepts, and continues through design, build, and QA. Every project runs one minimum QA path covering real startup, rendering, input, a complete loop, an outcome, restart, and explicit limitations. It does not require a human playtest or a separate approval report. Choose director when you want to pick the concept yourself.

Claude Code

/plugin marketplace add worldwonderer/novel-to-game
/plugin install novel-to-game@novel-to-game-skills
/novel-to-game:novel-to-game quick

Codex

codex plugin marketplace add worldwonderer/novel-to-game
codex plugin add novel-to-game@novel-to-game-skills

Kimi Code 0.27 or newer

/plugins install https://github.com/worldwonderer/novel-to-game
/reload
/skill:novel-to-game quick

Workflow

The orchestrator locks PRODUCT_BRIEF.md, then hands the adaptation through six stages with separate ownership. Concept, experience/level design, and art direction remain distinct, while acceptance checks only scope consistency and the six-effect minimum playable contract.

Novel → Source analysis → Concept → World design → Art direction → Build → QA → Playable game

Build targets the chosen runtime and prepares one verification entry point; QA runs it once and records the six minimum player-visible effects with real execution evidence. Capability-specific regression checks run only when that capability is actually adopted. No human-playtest gate or duplicate QA report is required. Source identity, public hosting, marketing, rights, subjective fun, and publication quality are not machine-proven by this QA record.

Skills

Artifacts

Each run creates a compact, self-contained adaptation workspace:

game-adaptations/<project>/
  PRODUCT_BRIEF.md
  analysis/SOURCE_BIBLE.md
  concepts/CONCEPT.md
  design/GAME_DESIGN.md
  design/ART_DIRECTION.md
  build/BUILD_BRIEF.md
  build/app/
  qa/verification.json
  _progress.md

Core design documents remain independent of any single model or game engine. The approved target runtime determines the implementation and QA environment.