Five Prompt Fixes From Running an LLM as a Game Narrator

Everyone tunes prompts by rewording the instruction and hoping the model listens. A developer running an LLM as the narrator of an interactive-fiction game found something better: stop polishing the wording, and change what the model actually sees. Five lessons came out of it, and they work well beyond games. Most of them take ten minutes to try.

The key idea is simple. A model follows the shape of what you show it, the cases you spell out, and the order you put things in. Your instructions come second. If your example, your rule and your layout all point in different directions, the model will usually follow the example, because that is the most concrete thing in front of it.

Old way vs new way

Old way: write one clear rule, add one balanced example, ask the model if the new prompt feels better. This feels reasonable, and it is how most of us start. The trouble is that every step relies on the model’s judgment of itself, and none of it gives you a number you can check.

New way: write a lopsided example, describe the failure in plain terms, list the specific cases, put stable text first, and measure the change with replays. Each step changes something you can see, and the last one tells you whether any of it worked.

Here is how each fix works in practice.

1. Show a one-sided example 🎯

The developer’s example showed one reason for and one reason against. The output gave exactly that pair 13 times out of 15, whatever the scene. A tense negotiation, a quiet walk through a market, a fight on a rooftop: each one got one reason for and one reason against, in the same order. The model copied the shape, not the instruction. Switching to a one-sided example broke the pattern.

How to do it: look at your example and ask what shape it has. Count the items, check the order, and notice the length. If the shape is not what you want repeated everywhere, change it. If you need variety, show two or three examples that differ from each other in structure, not just in topic.

2. Describe what a failure looks like

Telling the model to “honour the dice” produced failures that cost nothing. A roll would go badly, and the story would shrug it off. The fix was spelling it out: what the character reached for is not gained in this passage, and it costs something the reader can see.

How to do it: write one sentence that says what a bad result looks like in the output, not just what a good one is. A good test is to read the sentence and ask whether a stranger could spot the failure in a finished answer. If they could not, the sentence is still too vague.

3. Replace the general rule with the specific cases

A checker ignored “moves against a person are contests” three times out of four. The rule was correct, but it asked the model to scan every choice and decide which ones applied. When code listed the choices that named someone and handed those to the model, it acted on them.

How to do it: if a rule keeps getting skimmed, let your code pull out the matching cases and show those directly. A simple filter, a keyword match or a small lookup is often enough. The model then has no sorting job left, only a response to give.

4. Stable text first, changing text last 📌

The rules that never change go at the top, so they can be cached. Whatever changed this turn goes at the bottom. It is cheaper and it keeps the prompt tidy. It also makes debugging easier, because when something goes wrong you know the top half stayed the same and you only need to look at the bottom.

5. Don’t ask the model whether the prompt got better

Asking is a vibe check. Models tend to be agreeable, and a new version will often sound better simply because it is new. Instead, save a real moment, replay it with and without your change, and count how often the thing you wanted to change actually changed.

A quick test loop:

  • Save one real input that went wrong.
  • Run it 10 to 15 times on the old prompt.
  • Run it the same number of times on the new prompt.
  • Count the outputs that show the behavior you were after.
  • Keep the change only if the count moves clearly, for example from 3 out of 15 to 12 out of 15.

That last step is the one most people skip, and it is the one that tells you the truth.

Pick the one lesson that matches your biggest headache and try it on a single prompt today. Counting beats guessing every time! 🎯

If you want to see the narrator in action, the developer’s game is here: https://playselkie.com/?from=reddit-pe

Five prompt lessons from running an LLM as a game narrator in production
by u/Business-Pension-498 in PromptEngineering

Scroll to Top