← All posts
productaidesign

AI is not the author — it's the tool

Every AI tool promises to build your world for you. Ours doesn't. Here's why context and memory matter more than content generation.

The first thing most AI-powered tools tell you is what they can generate for you.

Write your lore. Name your NPCs. Describe your cities. Fill the blank page so you don't have to.

The Runekeeper doesn't work that way — and that's a deliberate choice.

What a basic AI subscription gets you

If you subscribe to ChatGPT or any of its competitors, you get a very good general-purpose text generator. Ask it to write a villain backstory, and it will. Ask it to name a city in a high fantasy world, and it will. Ask it for a list of plot hooks, and it will give you ten.

None of those outputs will know anything about your world.

The villain it writes won't know that your players already overthrew the last tyrant six sessions ago, or that the political vacuum that left behind is the whole point of the current arc. The city name won't know your world uses a Norse-influenced naming convention, or that you already have a city called Halvenmere two hexes away. The plot hooks won't know that one of your players is actively avoiding anything involving their character's dead sister.

A general-purpose AI is working with a blank slate every time. The output might be good. It won't be yours.

The context problem is the real problem

Worldbuilding is cumulative. Every decision you make narrows the possibility space for every future decision. The city you placed in the north makes certain migration patterns more plausible. The gods you established shape what taboos exist. The faction you introduced three sessions ago creates ripples that your players will eventually pull on.

When you sit down to prep a session, the challenge isn't that you have nothing to say. It's that you have everything — a sprawling body of decisions, lore, relationships, and history — and you need to quickly find and connect the pieces that matter right now.

That's not a generation problem. It's a retrieval and reasoning problem.

What Runekeeper is actually for

The Runekeeper reads your world.

Not a summary. Not a prompt you paste in. Your actual world data — the entities you've written, the relationships you've mapped, the sessions you've logged, the locations you've linked. All of it is embedded and indexed so that when you ask a question, the answer is grounded in what you built.

Ask "who has a reason to want the Thornwall garrison weakened?" and it doesn't invent factions from thin air. It looks at the factions in your world, their goals, their rivalries, and surfaces the ones whose existing motivations fit. The reasoning is yours. The Runekeeper just moves faster than you can by hand.

Ask it to help you write a scene for a location, and it writes into your established tone, your existing lore, your named characters. It's not generating a generic fantasy tavern — it's helping you write The Saltmark Inn in Halvenmere where the bartender is secretly passing messages to the Ember Compact.

The world is still yours. The Runekeeper just knows it.

Efficiency is not the same as automation

There's a version of AI-assisted worldbuilding that sounds appealing on the surface: push a button, get a world. Let the machine do the creative work so you don't have to.

We don't think that's what GMs actually want.

The world you're building is a message — a creative vision you're sharing with your players across months or years of play. The fiction matters because you made choices about it. The villain is compelling because you understand their pain. The setting resonates because it reflects something real about the kind of stories you want to tell.

What you want is not to be replaced in that process. You want to be faster in that process. Less time wrestling with your notes. Less time re-reading three articles to remember how two factions relate. Less friction between the idea in your head and the lore on the page.

That's what the Runekeeper is optimized for. Not generation — efficiency. Not automation — augmentation.

What TTRPGs are actually about

Tabletop roleplaying is one of the oldest forms of human storytelling. Sitting around a table, building a shared fiction together, improvising off each other's choices — it predates writing. It predates books. It's the thing humans have always done around fires.

The reason people play TTRPGs isn't to produce a great document. It's to have a great experience with other people. The stories that stick — the ones players still talk about years later — are almost never the ones the GM scripted perfectly. They're the moments that emerged from the table. The improvised NPC who became a beloved recurring character. The player decision that broke your plot in the best possible way. The session that ran three hours over because no one wanted it to end.

That experience is entirely human. No tool produces it. The GM who runs the table produces it — through the world they've built, the tone they set, the creativity they bring, the investment they have in their players' characters.

But here's the tension most GMs live inside: they want to run games at a quality that feels like the stories they love — the novels, the shows, the games that shaped them — and they have a few hours a week to prep.

Professional novelists can revise for months. Writers' rooms have eight people. GMs have Tuesday evening and a job tomorrow.

The gap between the story you want to tell and the time you have to prepare it is where prep collapses and sessions suffer. Not because the GM isn't talented. Because the tooling friction is too high.

The Runekeeper exists to close that gap — to give the casual storyteller enough leverage that the story they want to run is actually the story that gets run. So that the human connection at the table can happen at the quality it deserves.

Why this distinction matters

There are AI tools that will build a world for you. They're good at producing plausible, coherent-sounding fantasy content. If you need something quick and disposable, they work.

But a campaign isn't disposable. It's a living thing your players are invested in. The moment they pull on a thread the AI generated without context, it unravels — because there's nothing underneath it. No history. No intent. No connection to everything else.

The Runekeeper doesn't generate threads. It helps you weave the ones you've already started.

The story is still yours. The people around the table are still the point. We're just trying to make sure the prep doesn't get in the way.

— The Skryrún Team