World prompt examples

Your world prompt is where you write the standing rules and instructions that steer every AI tool working in your world. This page is a cookbook: copy the snippets that fit, edit them to taste, and paste them in under World Settings → World prompt.

Everything here is returned to agents by the get_world_instructions tool, so the more concrete and specific you are, the more consistent their work will be. Keep the whole thing focused — a tight prompt outperforms a sprawling one, and you have roughly 32 KB to work with (far more than you’ll need).

The snippets assume the data model: typed entities with property schemas, directed relationships, tags, and lore.

Set the workflow

Point agents at the right tools in the right order so they ground themselves before touching anything:

Before any world operation, call get_world_context to load the entity types,
relationship categories, and tag vocabulary — don't assume a type or value
exists. Search for an existing entity before creating a new one. When you're
unsure which entity type or relationship verb fits, ask me rather than guessing.

Naming conventions

Stop near-duplicate and inconsistently styled names before they pile up:

Name people "First Last" (e.g. "John Smith"), not nicknames — record
nicknames in the description. Name places after their common name ("Riverside Café"),
not their address. Use Title Case for all entity names. Before creating an
entity, search by name to confirm it doesn't already exist under a variant
spelling; if it does, update that one instead.

Formatting and data hygiene

Pin down how property values should be written, since property schemas describe fields but don’t enforce a format:

Write all dates as ISO 8601 (YYYY-MM-DD). Write phone numbers in E.164
(+15551234567). Put email in the `email` property, never in free text. Keep
descriptions to one or two sentences — put anything longer in lore. Leave a
property unset rather than filling it with "unknown" or "N/A".

Entity organization

Tell agents how you want the graph kept tidy — what to model as an entity, and how to tag:

Model recurring people, places, groups, and projects as entities; model one-off
mentions as lore on an existing entity, not as new entities. Apply tags from the
existing vocabulary — call get_world_context and reuse a current tag before
inventing a new one. Tag every person with their relationship to me (family,
friend, colleague) so I can filter later.

Relationship discipline

Keep the edges of the graph clean and preserve history:

Use the most specific relationship verb that fits the two entity types; fall
back to RELATED_TO only when nothing else applies. When a relationship ends
(someone leaves a group, a project wraps), set its `ended` date to mark it
historical — do not delete it. Reserve deletion for genuine data-entry mistakes.

Tone and voice

Lock in how lore and descriptions should read, so everything stays in one voice:

Write lore in close third person, present tense, matching the existing entries.
Keep descriptions factual and concise — no editorializing. For a creative world,
this is also where you set genre and canon rules (e.g. "magic always has a
physical cost; never describe it as free"); for a personal world, set the
perspective ("write about people warmly, in the first person").

Boundaries and confirmation

Put guardrails on what an agent may do without checking with you first:

Never create entities of type `event` without confirming the date with me
first. Do not edit or delete entities I didn't ask you to touch in this session.
If a request would create more than ten new entities at once, summarize the plan
and wait for my go-ahead before writing.

A full worked example

A compact, end-to-end prompt for a personal-tracking world. Adapt the specifics and paste it whole:

This world tracks the people, places, and events in my personal life. Keep it
accurate and tidy — it's a long-term record, not a scratchpad.

Workflow
- Call get_world_context at the start of every session before reading or writing.
- Always search for an existing entity before creating a new one.
- When unsure which type or relationship fits, ask me instead of guessing.

Naming & formatting
- People: "First Last", Title Case. Record nicknames in the description.
- Dates: ISO 8601 (YYYY-MM-DD). Phone numbers: E.164.
- Descriptions stay to one or two sentences; longer context goes in lore.

Organization
- Model recurring people, places, groups, and projects as entities; keep one-off
  mentions as lore.
- Reuse existing tags before creating new ones. Tag each person with how I know
  them (family, friend, colleague).

Relationships & history
- Use the most specific relationship verb available; RELATED_TO is a last resort.
- When a relationship ends, set its `ended` date — never delete it.

Boundaries
- Don't create events without confirming the date with me first.
- Don't touch entities I didn't ask about in this session.
- Summarize and wait for approval before writing more than ten entities at once.

Tip

Treat your world prompt as living. As you notice an agent repeating a mistake — a name styled wrong, a property left blank — add one line that addresses it. Small, specific rules accrue into a prompt that reliably keeps your world the way you want it.

See World prompt for how to set and edit it, and who on a shared world can.