Memory and instructions
Three kinds of document steer Manan. All live in the documents sidebar of the project.
| Document | Who writes it | When it is read |
|---|---|---|
| Memory | Manan | Every turn, in full |
| Instructions | You | Every turn (always) or when Manan decides it needs it (on demand) |
| Skills | You | Only when you invoke one with / |
Memory
Section titled “Memory”Manan keeps a per-project Memory document — its own notebook. When you state or settle something durable — a preference, a naming or style decision, a fact about the story or brand — Manan saves it at that moment as one short line, with at most a brief parenthetical to say so. It does not save one-offs, transient state, or anything the project already shows. Saving is free.
You can read Memory in the sidebar; the body is locked and a banner explains why. If a memory is wrong or stale, tell Manan and it rewrites the document — this applies directly even in Default mode. Deleting the Memory document wipes it; it is recreated empty at the next save. Every save is a version in the document’s history.
Project instructions
Section titled “Project instructions”An instructions document is one you write: how you want things named, worded, framed. Manan follows it the way it follows you, but the message in front of it always wins.
Create one from the sidebar and choose how it loads:
- Always — the full text is included in every turn. Keep it terse; the always-loaded set is capped at 8,000 characters in sidebar order.
- On demand — only the title and a one-line description are shown to Manan, which reads the body when a request touches it.
You can keep several. Manan changes an instructions document only when you ask, and tells you the change applies from the next message.
Save decisions from a conversation. The conversation picker has an action that asks Manan to distil the durable decisions from the chat into your project instructions. It reads the document first, keeps what’s there, adds terse imperative lines, and says exactly what it added. If nothing durable was settled, it files nothing.
Skills
Section titled “Skills”A skill is a document with a name (its / trigger, unique in the project) and a description shown in the / menu. Its body is a reusable prompt: a review checklist, a house style for narration, a scene template. Skills never load on their own — they run only when you invoke them.
Reference documents
Section titled “Reference documents”Character sheets, brand guidelines, tone notes — ordinary documents with an image bank. Every turn opens with an index of them (title, first line, picture count). Before writing copy, image prompts, or anything a reference could govern, Manan reads the relevant one and says which it followed. Pull one into a specific message with @. See Script and documents.