lineweave PROTOTYPE
Launch demo ↗
INDEPENDENT · WORKING PROTOTYPE

Find the gaps in
your game story.

Inspect branches, trace missing prerequisites, and prepare context-rich narrative reviews for Claude. Built for indie creators working with branching dialogue.

Try the interactive demo See how it works →
No sign-up required Runs locally in-browser
lineweave / narrative-reviewEXAMPLE
Trace the story4 connected scenes?
FINDINGS WITH EVIDENCE
Missing prerequisite

arrival → open_gate
The key was never acquired.

Broken destination

open_gate → ending_typo
No scene with this ID exists.

SAMPLE SCRIPT3 findings to review ↗
Built for focused workflows

Review the paths your players take.

Small script edits can leave a broken branch or an item used before it is acquired. Inspect these structural problems, then prepare the full story context for a human-reviewed Claude analysis.

Trace story paths

Find broken destinations, unreachable scenes, and a path that reaches a scene without its declared prerequisites.

Give Claude the context

Export world notes, dialogue, and branch findings in one review brief. Ask Claude for contradictions with scene IDs and source excerpts. You send the brief yourself.

Private by design

Everything in this demo runs in your browser. Script text is not transmitted to a server or sent to an AI model.

Narrative QA · working prototype

A missing key. A broken ending.

Try the original four-scene example with three planted findings. Load the corrected version to see the difference. These checks use declared rules, not AI interpretation.

LOCAL CHECKS
Findings with paths—
How the script format works

entry names the starting scene. choices links scenes with to. requires lists facts expected on scene entry; sets adds facts after its dialogue. All choices are unconditional. Facts persist: removal, numeric conditions, and timed events are not modeled. Blank choices marks an ending. JSON examples are editable. At most 200 scenes and 1,000 distinct path states are checked; incomplete analysis is explicitly flagged.

Download and inspect this brief before sending it to Claude yourself. It asks for continuity and character-knowledge findings with source excerpts. Semantic review and automatic Claude API integration are not performed by this website.

Try it now

A prototype you can actually use.

Paste your own lines or load the example. Group them, inspect the result, and export it — all without leaving this page.

Dialogue workspace
ALL LOCAL · NO API
0 lines
Organized batches0 batches
Your batches will appear here.
Ready for input
This demo prepares scripts and translation briefs locally. It does not call Claude or translate automatically. If you paste a brief into an AI service, that service will receive its contents under its own terms.

From preparation to translation

Give every line its context.

Add a scene and glossary, then copy the brief into your own Claude conversation. No API key or paid integration required by Lineweave.

GENERATED LOCALLY

1. Build and inspect the brief. 2. Paste it into Claude yourself. 3. Review meaning, character voice, and placeholders before using any translation. Input is cleared when this page reloads.

After Claude responds

Catch the details that break a scene.

Paste Claude’s JSON response to check line IDs, missing placeholders, and glossary matches against your current script. These are format checks; meaning and tone still need human review.

The example is hand-written with two intentional errors, not a Claude result. Loading it replaces the demo script and glossary. Glossary checks use exact text matching and may need your judgment.

Review findings—

About the project

Context for every conversation.

Lineweave helps indie game creators review branching scripts before release. The current prototype checks declared story structure locally and prepares a Claude review brief. Localization preparation and format checks are included as supporting tools. You decide which findings need a rewrite.

HTML / CSS / JavaScriptBrowser-basedOpen to iteration

Before the next rewrite

Follow the path. Find the gap.

Start with a four-scene example. No account required.

Check the story ↗