đïž Chat Mechanics & Instructions â The Friendly Power-User Guide (SFW)
Think of your chat like a small stage play: you set the roles, pin the script beats, and direct the next scene. The tips below help you keep stories consistent, engaging, and easy to steerâwithout micromanaging every line.
1) đ Auto-Memory Rhythm (What it is & how to keep it on track)
Many systems maintain an auto-summary or auto-memory that refreshes periodically (e.g., after a set number of AI messages). That memory is the modelâs âworking notes.â Itâs greatâuntil it wanders.
Your goal: keep the memory aligned with your core premise.
â Simple routine to stay aligned
- Watch the refresh cadence. When youâre one message away from a rollover (e.g., after 19 AI messages), run a short recap request.
- Use a lightweight recap command, e.g.:
/analyze â please summarize the story so far in 5â8 bullet points. Start from: [how the roleplay began], End at: [the latest major line or beat]. - Why it works: the system reads the recap before continuing, so your âheadlightsâ point back at the road.
Tip: Keep recaps concise and factual. Youâre not writing prose; youâre refreshing the compass.
2) đ§ Utility Commands (Your all-purpose toolkit)
/analyze â the story radar
Use it to ask the model about the current state or likely reactions based on whatâs been established.
- Examples:
/analyze â given the last scene, what is [Character] likely planning next?/analyze â if [Event] happens, how might [Character] respond?
- Great for: sanity checks, tone checks, and forecasting plausible outcomes.
Note: Treat answers as probable rather than absolute. Youâre still the director.
/direct â the time skipper & scene shifter
Move the story forward when youâre low on inspiration or want to change location/time.
- Examples:
/direct â they walk home from work, chatting about the presentation./direct â one week passes; the festival begins today.
- If the response misses the mark, undo/refresh that single turn and nudge again with 1â2 clarifying details.
3) đ Pinned Memories (Your living rulebook & road map)
Pinned memories are authoritative guidance the model re-reads frequently. Think: session bible.
Recommended order (top â bottom)
- đ« Bans & Safety Rules (non-negotiables)
- â Approvals / Overrides (allowed exceptions, canon corrections)
- Core Premise & Key Facts (what the story is about; whoâs who)
- Character Anchors (traits that should not drift)
- World & Setting Facts
- Supporting Cast / NPC notes (short, functional blurbs)
The model tends to read top-down, so lead with the immovables.
Example skeleton (SFW)
[ BANS ]
- No internal monologue access for the userâs persona.
- Do not invent private actions for the userâs persona off-screen.
- Stay SFW: no explicit sexual content or graphic violence.
[ APPROVALS / OVERRIDES ]
- If continuity conflicts arise, prefer pinned facts over past ad-libbed lines.
- Use the userâs latest correction as canon.
[ CORE PREMISE ]
- Small-town slice-of-life: two colleagues prepare a community showcase.
[ CHARACTER ANCHORS ]
- Clara: empathetic, methodical; hates being late; collects enamel pins.
- Ezra: witty, cautious optimist; sketches ideas before speaking.
[ WORLD NOTES ]
- Setting: modern day, coastal town; seasonal festival in 2 weeks.
- Work: local arts center with a stage, café, and workshop studio.
[ SUPPORTING CAST / NPCS ]
- Mira (manager): organized, direct; keeps schedules color-coded.
- Theo (neighbor): hobby baker; supplies pastries on Fridays.
Keep it under the platformâs character limit. Write crisply. Emojis are optional flairâuse them only if they help you scan.
4) 𧩠Boundaries, Perspective & Safety Locks (Make drift nearly impossible)
Use a short âlocksâ section to guard POV, time, and tone.
[ LOCKS ]
- Perspective: the AI only speaks as the designated character(s) in first person.
- No assumptions about the userâs private actions, thoughts, or backstory.
- Time flow: progress sequentially (day by day) unless the user directs a skip.
- Relationship pacing: slow-burn arc; milestones occur only when the user initiates.
If the model slips, reassert the lock once and proceed. Donât argue; guide.
5) â© Pacing Phases (SFW relationship & story scaffolding)
Break your arc into friendly, human milestones so the model doesnât sprint.
[ STORY / RELATIONSHIP PHASES ]
Phase 1 (Days 1â30): introductions, shared tasks, light banter.
Phase 2 (Days 31â60): small favors, inside jokes, supportive moments.
Phase 3 (Days 61+): trust milestones, heartfelt conversations, optional romance beats (only if user opts in).
You can tune durations, rename phases (e.g., âSetup â Growth â Payoffâ), or swap romance for friendship arcs.
6) đ Persona Sheets (for player or main character)
Keep it useful, short, scannable. The goal is âconsistent callbacks,â not a novella.
Template
[ NAME ]: Rowan
[ VIBE ]: reflective, kind, a little awkward before coffee
[ TELLS ]: taps pen when thinking; adjusts glasses when nervous
[ LOOK ]: short wavy hair; comfy cardigans; messenger bag
[ HOOKS ]: volunteers at community garden; loves local history trivia
[ LINES TO AVOID ]: boasting; breaking promises; talking over others
Anything here becomes âsurface canonâ the model can reliably reference.
7) đ§č Custom Instructions (one-off directorsâ notes)
Use custom instructions to insert a beat once, then remove them to avoid loops.
- Good:
[Custom]: The power flickers during the rehearsal; everyone adapts. - Afterwards: delete that line from your instruction pane.
If you forget to remove it, the model may replay the same beat in new scenes.
8) đïž Sliders You Can Safely Adjust
- Tone / Warmth: sets how cozy or formal the voice feels.
- Response Length: shorter = snappier pacing; longer = more descriptive scene work.
- Creativity: higher = bolder leaps; lower = steadier recall.
If the model truncates, follow up with:
âContinue from the last sentence without rewinding.â
9) đ§Ș Troubleshooting (fast fixes)
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| Character drift | Pinned facts too light or buried | Move anchors higher; add a 5-bullet recap via /analyze |
| Extra characters appear | Duplicate tags/roles implied | State âsolo sceneâ or name exactly whoâs present |
| Time jumps | Model trying to be helpful | Reinstate âsequential time onlyâ lock |
| Tone too forward/too flat | Global tone not pinned | Add a âVoice & Toneâ block (2â3 lines) |
| Loops/repeated beats | Forgotten custom note | Remove the directorâs note; ask for a fresh transition with /direct |
10) đïž Reusable Mini-Templates
A) Recap Nudge
/analyze â please summarize the story so far in 5â8 bullets.
Start from: [origin hook]
End at: [last notable line or scene]
B) Scene Shift
/direct â the next morning, we set up the stage lighting test together.
C) Reaction Probe
/analyze â based on pinned traits, how would [Character] likely respond to [Event]?
D) Continuity Correction
Please align with pinned facts: [specific fact].
Retcon the last line minimally; continue the scene.
11) đŠ Example âAll-in-Oneâ Starter Pinned Block (SFW)
[ SAFETY & BANS ]
- SFW only; no explicit sexual content or graphic violence.
- No inner monologue access or private actions attributed to the user.
[ LOCKS ]
- First-person voice from named character(s) only.
- Sequential time; no flashbacks/skips unless directed.
- Respect user choices as canon.
[ CORE ]
- Cozy workplace slice-of-life at a community arts center before a local festival.
[ ANCHORS ]
- Jamie: energetic, collaborative, doodles stage layouts.
- Noor: calm, precise; carries a pocket notebook; dislikes last-minute changes.
[ WORLD ]
- Coastal town; rehearsal evenings Tue/Thu; café next door (good cinnamon rolls).
[ NPCS ]
- Manager (Alex): kindly strict; color-coded schedules.
- Neighbor (Rin): offers spare cables and tech help.
[ TONE ]
- Warm, encouraging, lightly humorous; show-not-tell; gentle pacing.
12) Final Advice (so you donât need this doc every time)
Stay SFW by default. It keeps public sharing simple and moderation happy.
Pin the non-negotiables first. (Bans â Locks â Core)
Nudge memory on a cadence with short, targeted /analyze recaps.
Direct scenes sparingly with /direct to keep momentum.
Avoid clutter. Remove custom notes once theyâve fired.
Iterate in small steps. One change at a time beats wholesale rewrites.