DesireBorn writes erotica with you, not for you. Give it a starting idea, and it writes one section at a time - you steer after each one.

Guides

How to prompt a long erotic novel that does not fall apart in chapter five

Chapter five is where AI fiction goes to die. The first chapter is fine, because the model has your whole setup in front of it and nothing else. The second is fine for the same reason. Somewhere around the fifth, the setup has scrolled out of reach, the story has generated enough of its own detail to contradict itself, and the sentence you typed at the start about the sister who must never find out has been forgotten by the only thing that ever knew it. Most people blame the prompt and write a longer one. That is usually the wrong fix.

This guide is about the right one. It assumes you are using an engine that keeps a story state of its own, which is what DesireBorn does; the guide to story state explains that machinery. Here the question is what you should give it, and what you should not.

One line is a complete starting point

Start with what you actually want. "A reunion between two people who never stopped wanting each other." "A rigger and a woman who has only seen it done in photographs." "Her best friend's older brother, the summer she comes home to sell the house." That is a premise. It has two people, a pressure and a reason for them to be in the same place, and it is enough for the engine to plan a whole story from.

Readers who come from chat-style tools often arrive with a habit of writing a thousand words of setup: every character's history, eye colour, childhood wound, the exact sequence of scenes. On a chat tool that is necessary, because you are the memory. On a story engine it is mostly harmful. Every detail you fix is a detail the story can no longer discover, and a story that discovers nothing is a story you already wrote, delivered back to you slower. Give the engine the idea and let it fill in what you left open. It will choose to fit your line, and you can correct it between sections if it chooses wrong.

What is worth specifying

Three things, in our experience, and only three.

The dynamic between them, if you care about it. "She has the money, he has the patience" is worth a line. "They were together once and it ended badly" is worth a line. This is the thing the engine will otherwise invent, and it is the thing you are least likely to be happy with if it invents it differently from what you had in mind.

The ending, if you have one. The engine plans an ending before it writes the first section, and it aims at it. If you want the story to end with her leaving, say so in the special instructions field, and the plan will bend toward it from the start rather than lurching toward it in the last section. If you do not have an ending in mind, leave it out; the engine will pick one and you will find out what it was.

The things you never want. Words, acts, phrasings. The special instructions field has a placeholder that says forbidden phrasings, things that must be included, how it should end, and that order is right. A forbidden phrasing travels with the story into every section; you write it once. On DesireBorn Bound this is also where your own limits go, and the guide to BDSM with your own limits is entirely about that field.

Everything else, people, tone, point of view, tense, how much should happen per section, is optional and can be left open. Explicitness is the exception: it has a default, and you probably want to choose it yourself. The guide to heat levels is about that choice.

Steering is a scalpel, not a steering wheel

After each section there is a field for what should happen next. The temptation is to use it every time, and to use it to narrate: "she goes to the kitchen and finds the letter and reads it and confronts him." That is writing the story in prose and asking the engine to typeset it. It works, but it produces exactly the stiffness people complain about, because the engine is being told what to do at the level where it is best left alone.

Use it for the turns. "Let him find the letter." "Slow the tension down." "Bring her sister back." "Change who is in control tonight." One sentence about direction, not a paragraph about events. Then leave the next few sections open and read. The engine continues from its own state and from what you said; the story keeps its own voice. The button for an empty field is called Surprise me, and it is the setting most long stories are best read on.

The other use of steering is correction. If in section three the engine has decided he is a widower and you wanted him divorced, say so there: "He is divorced, not widowed." The correction is carried forward. Correcting early is cheap; the same correction in section fourteen means the story has built on the wrong fact for eleven sections, and while the engine will adjust, the reader will remember.

Why longer prompts make longer stories worse

It is worth understanding why the thousand-word setup fails, because the reason is not obvious. A model writes each section against a context: the plan, the story state, the recent sections, your instructions. Everything you put in the setup competes for that context with everything the story has since established. A setup that specifies twelve characters is twelve characters the state has to carry whether the story uses them or not, and twelve opportunities to contradict a detail you wrote once and forgot. A setup that specifies two people and a pressure gives the state room to hold what the story actually did.

The other failure is stranger. A very detailed setup tends to produce a story that keeps restating it. The model treats your description as the thing it must prove it read, and so every section reminds you that he has grey eyes and a scar. Leave the eyes out and the story will give him something more interesting to be recognised by.

The shape of a long story on DesireBorn

Sections are the unit. You set how much should happen per section, or leave it open; the engine plans a beat for each and an ending to aim at, and writes them one at a time. When it reaches the ending, you can extend the story and it plans onward from what actually happened rather than from what it once intended. A story can also be marked finished by you, which is different from the plan being complete, because you are the one who decides when it is done.

Rewrites are kept, not thrown away. If you regenerate a section, the old one is marked superseded and stays in the record; nothing you disliked is lost, and nothing is silently overwritten. Most readers never look at superseded sections, but knowing they exist changes how freely you regenerate.

One thing does not bend for any prompt. Every character in a sexual context is an adult, and that cannot be turned off, softened or configured, by you or by us. Within that, everything lawful between consenting adults is yours to set up, at the explicitness you choose. No shame. Not no limits.

What happens to what you type

Your premise, your special instructions and every steering line are part of the story, and they are stored the way the story is. Your stories are encrypted at rest. We can read them to write them. Nobody else can read them. The privacy guide walks through exactly what that means, and what it does not.

So: one line, the dynamic if it matters, the ending if you have one, the things you never want. Then read, and steer at the turns.