SMF·LIVINGWRITER
Can a prompt replace LivingWriter?
AI writing — grammar, editing and long-form writing
Exhibit tracking slip
Verdict
LivingWriter's two distinctive habits are cheap to build and genuinely useful: you start from a story-structure template — the Hero's Journey, Save the Cat, a three-act skeleton — and get its beats as a working outline, and typing a character's name anywhere in the manuscript links it to that character's page automatically. Neither needs a model. What you give up is what every writing tool in this category gives up: the sync and the phone, on work you cannot afford to lose.
Exhibit A — The prompt
Received on31.07.2026Build a local novel-writing application organised around story-structure templates and automatic element linking. No AI features.
Structure templates: a template is a named list of beats, each with a title, a description of its narrative purpose, and a suggested position as a percentage of total length. Ship three, defined in an editable file rather than in code: a three-act structure, the Hero's Journey, and a beat sheet in the Save the Cat shape. Starting a project selects a template and creates its beats as an outline.
Beats and scenes: scenes are written against beats. A beat shows its target position, its actual position by cumulative word count, and its drift — a midpoint beat sitting at 63 percent of the manuscript is the kind of structural problem this view exists to surface. A beat can hold several scenes, and a scene can sit outside any beat.
Story elements: characters, locations, objects and factions, each with a name, a list of aliases, arbitrary user-defined fields, and free-text notes.
Automatic linking, which is the second distinguishing feature. As the writer types, detect element names and aliases in the manuscript and mark them as links, without changing the underlying text — the file stays plain Markdown, and the links are an overlay computed from the element list. Clicking a mention opens that element beside the editor. Each element's page lists every scene it appears in, in manuscript order, so a character who vanishes for twelve chapters is visible at a glance. Handle ambiguity by asking once and remembering: if "May" is both a character and a month, the writer resolves it and the choice is stored per context.
Writing view: distraction-free editor for one scene with the beat's description in a collapsible strip, so the writer can see what the beat is supposed to accomplish.
Progress: word counts per scene, beat and manuscript against targets, daily history, and a projected finish date from the recent average.
Storage: SQLite as the working store plus an automatic export of the manuscript to plain Markdown files on every close, so the text is never trapped where only this application can read it. Timestamped snapshots before any structural change.
Export: single Markdown, compiled DOCX in standard manuscript format, and a full JSON backup including elements and beats.
Out of scope: cloud sync, mobile apps, collaboration, and any AI writing or editing feature.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 cloud sync and the mobile apps
- B.2 backup held somewhere other than your own machine
- B.3 the collection of structure templates maintained and expanded over time
- B.4 sharing a manuscript with an editor inside the tool
Prior art
Exhibit C — Why people still pay: polish, integrations, and proprietary language models
Because a manuscript represents a year of work and fifteen dollars a month for it to exist in three places is cheap. Nobody regrets that subscription; plenty of people regret a failed disk.
Questions
Can I import a LivingWriter manuscript?
The prose exports as DOCX and comes across fine. Story elements export as a list but not with their relationships or custom fields intact, and the outline's beat structure has to be re-created — an hour or two for a work in progress.
Does the beat-drift view actually help?
It is the most useful thing in the build. Structural problems in a first draft are almost always pacing, and seeing that your midpoint landed at 63 percent is a concrete, fixable observation in a way that "the middle sags" is not.
What does it cost to run?
Nothing. A SQLite file and a Markdown folder on your own machine, no keys and no server. The automatic Markdown export exists so that even this application going away does not put the manuscript at risk.
What is the one thing that does not survive the rebuild?
Off-machine backup. LivingWriter's sync means a dead laptop costs you a day; here it costs you the manuscript unless your own backups are working, and the snapshot directory sits on the same disk as everything else.
Related tools
Receipt