(Generated using SpicyBot at SpictChat.ai.)
Here’s a structured breakdown of best practices for the core bot creation fields.
FIRST MESSAGE / GREETING
(Max: 2,000 tokens) This is your most powerful tool for setting behavior. It establishes:
- Tone and voice — Show, don’t tell, how the character speaks
- Format consistency — Demonstrate exactly how narration/dialogue should look
- Dynamic with user — Position the {{user}} immediately
- Scene stakes — Hook with action or tension, not exposition
Best Practices:
- Open in-scene, not with backstory dumps
- Use {{char}} and {{user}} variables consistently
- Include sensory detail and character action
- Match the exact formatting you want throughout (asterisks for action, quotes for speech, etc.)
- Minimum 2 paragraphs for proper anchoring
- Avoid speaking for {{user}} – this trains the model it can control them
- End at a decision point or moment that invites response
Red Flags:
✗ Hi, I’m [name] and I…
(flat introduction)
✗ Writing {{user}}’s actions or dialogue
✗ Contradicting what you’ve set in Personality/Scenario
✗ Very short openings (under 100 words = weak anchoring)
PERSONALITY FIELD
(Max: 5,000 tokens) This is the behavioral engine—directives over prose every time.
Structure Priority:
- Core identity — Who they are at the deepest level
- Behavioral directives — How they act, react, decide
- Speech patterns — Voice markers, vocabulary, quirks
- Relationship stance — Default toward {{user}}/others
- Hard boundaries — What they will NEVER do
Best Practices:
- Use shorthand notation:
Blunt. Impatient with small talk. Speaks in clipped sentences.
- Separate traits with periods or line breaks, not flowing paragraphs
- Prioritize actionable directives over descriptive fluff
- Include contradictions that create depth (
Loyal but distrustful. Protective yet emotionally distant.
) - Specify emotional range explicitly (
Rarely angry—when pushed, goes cold, not loud.
)
Red Flags:
✗ Prose-heavy bios that waste tokens on atmosphere
✗ Vague descriptors (mysterious,
complex
) without behavioral examples
✗ Listing likes/dislikes without showing HOW they manifest
✗ Contradicting what you established elsewhere
SCENARIO FIELD
(Max: 4,000 tokens) Context and framing—this is WHERE and WHY, not WHO.
Core Functions:
• Setting — Time, place, world state
• Situation — What’s happening right now
• Stakes — Why it matters
• Relationship context — How {{user}} fits in
• External pressures — What forces act on the characters
Best Practices:
- Establish concrete circumstances:
Modern city. Underground fighting circuit. {{user}} owes money to dangerous people.
- Define power dynamics clearly:
{{char}} holds leverage. {{user}} needs something only they can provide.
- Set ongoing tensions that generate scenes:
Rival faction moving in. Clock ticking on deadline.
- Include world rules that affect behavior:
Magic is illegal. Getting caught means death.
Red Flags:
✗Repeating personality info here—wastes tokens
✗ Overly broad settings (fantasy world
) without specifics
✗ No inherent conflict or tension generator
✗ Contradicting what Personality established (e.g., distrusts everyone
in Personality but immediately trusts {{user}}
in Scenario)
FIELD RELATIONSHIPS
Think of them as layers:
Personality = Internal (who they ARE)
Scenario = External (what SURROUNDS them)
First Message = Proof (SHOWS both in action)When these align, the bot anchors fast. When they contradict, the model hallucinates.
COMMON PITFALLS CHECKLIST
Before publishing, verify:
□ No conflicting directives across fields
□ First Message doesn’t speak for {{user}}
□ Formatting in First Message matches your intent (and is consistent)
□ Personality uses directives, not just description
□ Scenario adds new info, not repetition
□ Character has clear motivation/stakes
□ Token usage isn’t bloated where shorthand works
QUICK OPTIMIZATION TIP:
If you’re running high on tokens, convert prose to shorthand:
Before: She is someone who tends to be very impatient when people take too long to get to the point, and she often interrupts them mid-sentence
After: Impatient. Interrupts rambling. Values brevity.
Same information, far fewer tokens.
