In Notion, the equivalent of a system prompt is the Instructions page: a page your Notion Agent reads in every chat, where you set tone, formatting and rules once instead of retyping them. Keep it short, specific and positive, then test it on a real chapter.
This guide covers how Notion's Instructions work, a five-part structure for a book-writing assistant, a copy-ready example, and the limits to know about. Product behavior in this area changes often, so I've based the details on Notion's own help pages as of November 2026; check them before relying on a menu path.
What is a "system prompt" in Notion?
It's the Instructions page, which tells your personal Notion Agent how to respond by default. According to Notion's help center, Instructions cover "tone, formatting, and rules to follow", and your agent uses your active Instructions page in every chat. You can have multiple pages but only one is active at a time, and you can switch any time.
| Feature | What it is (per Notion's help) | Use it for |
|---|---|---|
| Instructions | Persistent preferences applied to every Notion Agent response, your "default mode" | Voice, formatting, standing rules |
| Skills | On-demand actions you trigger for a specific task or selection | Reusable prompts, like "polish this section" |
| Custom Agents | Autonomous agents that can run in the background, be triggered by events, and be shared; each has its own Instructions | Scheduled or event-driven jobs |
Setup is short. Go to Settings, then Notion AI, then Add Instructions, and choose Create your own, use a template, or use an existing page. From an existing page you can also use the "…" menu, then Use with AI, then Use as Agent instructions. If you share the page, it doesn't change anyone else's agent unless they set it as their own, and Notion warns that if other people can edit your instructions page, their edits change how your agent responds. Workspace owners may also be able to set default instructions for the whole workspace; check your plan and settings.
What should a book-writing instructions page contain?
Five parts: who the assistant is, how it should sound, how it should format, what rules it must follow, and where to look first. This mirrors the structure OpenAI's prompt guide suggests for a developer message (identity, instructions, examples, context), adapted to Notion. Notion's own best practices agree with the spirit: think of Instructions as your default mode, start with what you want rather than what you don't, be specific, and keep it short.
| Part | What to write | Example line |
|---|---|---|
| 1. Role | The job and the reader, in a sentence | "You are my drafting assistant for a practical guide for new freelancers." |
| 2. Voice | Concrete, observable traits | "Plain, warm, second person. Sentences mostly under 20 words." |
| 3. Formatting | Structure you want every time | "Use H2 headings, one bold takeaway per section, a 'Try this' action at the end." |
| 4. Rules | Positive instructions plus a few hard limits | "Use only facts in my notes. If unsure, write [DATA NEEDED]." |
| 5. Where to look | Pages the agent should check first | "Check the Style Guide and Chapter Plan pages before drafting." |
For the role line, note that research on personas found they don't reliably improve accuracy; see should I tell AI to act as an expert? A one-line job description is plenty. Put your effort into voice, formatting and rules.
What does a good example look like?
A page under about 150 words that you could read aloud in a minute. Here's an example written for illustration (adapt the details to your book; it's not a Notion template):
My Notion AI: Book assistant
Role: You help me draft and edit chapters of a practical guide for new freelancers.
Voice: Plain, warm, direct. Second person ("you"). Mostly short sentences. One concrete example per section.
Format: H2 headings phrased as questions. Start each section with a one-sentence answer in bold. End each chapter with a "Try this" box (one action, five minutes).
Rules:
- Use only facts from my notes pages. If something is missing, write [DATA NEEDED: what] and keep going.
- When editing, change only what I ask. Show changes as a list before rewriting.
- Ask one clarifying question if the request could mean two things.
Check first: "Style Guide", "Chapter Plan", and the current chapter's notes page.
Notice what's missing: no stack of adjectives, no long "never do" list, no paragraph about being helpful. Notion says to revisit your instructions as your preferences evolve, and a rule of thumb from its help page is useful here: if you'd correct the same behavior twice, add it to your Instructions.
How do I test and tune the instructions?
Run the same sample prompt before and after each change, and change one rule at a time. Pick a paragraph from your own draft, ask for the same edit, and compare. If a rule isn't followed, try rewording it positively ("use short sentences" rather than "don't write long sentences"), moving it higher, or checking for a contradiction with another rule. Our guide on reusing a prompt across ChatGPT, Claude and Gemini explains why the same words can behave differently in different tools, which also applies if you copy the page into another assistant.
Keep a "tests" section at the bottom of a separate page, listing three sample requests and what a good answer looks like. That's the closest you'll get to a regression suite for a prompt. When your instructions grow past what a single page can hold (voice rules, chapter specs, research facts), consider moving the book's structure into its own pages, as covered in the Notion book writing template.
What are the limits of Instructions?
They shape defaults, not outcomes, and they only cover your own chat. Notion's help notes that personal Instructions don't affect Custom Agents, which have their own. They also can't guarantee that a rule is followed every time, and they aren't a substitute for a staged writing workflow, which is the idea Interactive eBook Builder is built around: Agent A Spec Builder plans, Agent B Drafter writes and Agent C Polisher edits. For planning and polishing roles in particular, see how to structure system prompts for chapter planning and editorial polish.
If you'd rather not assemble a prompt system yourself, the Configuration Hub in Interactive eBook Builder holds the book's settings and its agent instructions are editable, so voice, structure and rules travel with the project rather than living in a single chat. It's a separate product from Notion, so think of it as an alternative to this setup, not an add-on.
Before you hit send
- Is your instructions page under roughly 150-200 words?
- Does each rule say what to do, not only what to avoid?
- Are voice traits concrete enough to check ("under 20 words per sentence")?
- Did you test it on the same sample paragraph before and after changes?
- Is the page private, or are you sure who can edit it?
The takeaway: treat Notion's Instructions as a short style sheet, not a manifesto. Write it, test it, and edit it the moment you correct the same thing twice.