Janitor AI Lorebook Template (2026): Keys & Examples

People searching Janitor AI Lorebook template want something they can adapt, not a vague promise that more code creates better roleplay. This guide gives a small, testable structure for keys, conditions and content. It complements the Janitor AI Lorebook guide, the authorized export guide and the Lorebook troubleshooting guide without duplicating their main intents.

What a good Lorebook template is for

A Lorebook template is a repeatable entry pattern, not a magic personality upgrade. Use it for world facts that matter only when a place, faction, item or event appears. Do not use it to hide stable identity, every reply instruction or private creator content. A small template is easier to review, migrate and debug than a giant script.

The four fields every entry needs

Every entry should have a human-readable label, primary keys, optional secondary conditions and standalone content. Add enabled state, constant, order, position, probability and depth only when you understand the behavior. Preserve the source note and license for content you did not create.

Write keys that do not overfire

Choose rare names and phrases instead of common words. One strong key is easier to test than ten approximate keys. Add synonyms only when they are natural. Secondary keys should narrow a context, not introduce an unrelated topic. Regex is optional and should come with false-positive tests.

1. Choose one rare primary key.
2. Add one synonym only if users naturally type it.
3. Keep secondary conditions separate.
4. Test a negative control that should not activate.
5. Narrow broad keys before increasing any token budget.

Make content standalone and useful

Write content as if the model will never see the key label. State who or what the entry describes, the essential fact, the consequence and the scope. Split a long history into entries by subject. Avoid contradictions with the character card and do not paste executable scripts into ordinary lore text.

Tune settings one variable at a time

Start with a small scan depth, budget and default insertion position. Keep probability at 100% while debugging so randomness does not hide a key problem. Turn recursion off for the baseline. Change one setting, resend the same message and record what changed before optimizing further.

A copy-ready safe template example

The example uses fictional Harbor Council facts and is safe to replace with your own world. Keep the structure, then substitute your permitted names, keys and content. Do not copy a creator’s closed entries or treat a public character page as permission to extract its hidden Lorebook.

Title: Harbor Council
Primary keys: Aster Harbor, harbor council
Secondary condition: the council is being discussed
Content: Aster Harbor is governed by five council seats. A tie pauses new laws until the harbor bell is rung.
Use: add this entry only when the place or council matters to the current scene.

Prove the template with an eight-turn test

Use the eight turns below after every meaningful template change. Check absent keys, exact keys, synonyms, conditions, collisions, scene changes, corrections and a reopened chat. Record activation, insertion location, token use and reply quality. A passing template activates when needed and stays quiet when it is not needed.

A template cannot fix a weak model, a broken login, a contradictory card or an unauthorized source. If the real goal is direct character chat rather than maintaining a Lorebook, try the LumiChat character library. LumiChat is a separate platform and does not unlock Janitor AI content.

FAQ

What is the best Janitor AI Lorebook template?

Use the shortest entry structure that clearly defines keys, conditions, standalone content and a test.

How many keys should one entry have?

Start with one distinctive key and add only natural synonyms that pass a negative-control test.

Should every Lorebook entry be constant?

No. Constant entries spend context on every request and should be rare.

What belongs in Lorebook content?

Keyed world facts, locations, factions, items and events that matter only in relevant scenes.

Why does my template overfire?

Broad keys, constant state, large scan depth or recursion may activate it too often.

Can I use a Script as a Lorebook template?

Script logic is a separate layer. Ordinary lore text does not execute JavaScript.

Can I copy a public creator template?

Only when the creator allows reuse. Public visibility is not a license for hidden content.

Can LumiChat import this template?

This guide makes no direct import promise; LumiChat is a separate hosted character-chat service.