Lore & Examples

This is where a character becomes more specific. It is also where creators most often add too much and make the setup harder to control.

Alternative Greetings

• Optional alternate openers users can swap between.
• Useful when one character supports several starting moods or scenarios.

Use these when the character genuinely supports multiple valid entry points, not when you are still undecided about the core greeting.

Lore

• Additional background, scenario, and world details.
• Counted in the total token estimate.
• Best for context that matters, but does not belong in the description or greeting.

Lore works best when it supports the scenario rather than trying to describe everything at once.

Message Examples

• Structured example exchanges between user and character.
• Best for showing response rhythm, formatting, and recurring behaviors.
• Stronger than vague instructions when you want a very specific style.

If the character should sound a certain way, examples are often the clearest way to prove it.

Token Budget

Studio exposes a live token summary with two numbers:

• Permanent currently tracks the name and description portion.
• Total includes the name, description, greeting, lore, and message examples.

The app's current rule of thumb is:

• 1 token ~= 4 characters

Treat the counter as a practical writing budget, not a perfect model of runtime behavior.

Signs You Should Trim Instead of Add

• the lore repeats what the greeting already says
• the examples all prove the same behavior
• the character feels muddier after each edit
• you cannot tell which field is actually doing the work