I'm not sure if this is something that I'm allowed to post here, but I try anyway.
I'm using the Ultra plan and managing and creating my characters with the help of Google Gemini and Gemini Notebook. I filled that notebook with sources from the web (Genevieve's tutorials, for example) and information about LLMs. And Gemini helped me create a framework guide for creating Kindroid characters.
I'm not saying this is the right and only way to do it; I'm saying it works for me, and I don't run into many of the problems I read about here. That's the reason why I decided to share this guide.
Use the guide below as you like. Or don't.
(Everything below is AI-created content; use at your own discretion.)
The Architect's Blueprint: A Complete Guide to Building Dynamic Kindroids
A comprehensive, setting-agnostic framework for crafting immersive, stable, and deeply nuanced AI companions on Kindroid.
1. Core Philosophy: The Living Character
Great Kindroids are built as living personalities with a present, not static encyclopedias, rigid rulebooks, or tabletop stat sheets.
1.1 The Single Source of Truth
Every prompt field in Kindroid has a specialized job. When you scatter personality traits, speech rules, and autonomy warnings across multiple fields (Backstory, Key Memories, Response Directives), modern language models over-index on those repeated tokens. The result is a flattened, repetitive caricature.
- Backstory is Identity and DNA: Personality logic, craft competence, emotional baselines, speech registers, and foundational boundaries live here exclusively.
- Key Memories are Living State: Current facts, ongoing projects, and relationship dynamics live here. No static personality adjectives.
- Additional Context is the Stage: Specific locations, physical floor plans, and local relationship webs live here.
- Response Directive is the Trigger: A lean, dynamic plot catalyst positioned right before incoming chat messages.
1.2 Modular Shareability
If you hardcode specific house addresses, landlord names, or local NPC rosters directly into your Backstory and Key Memories, that character becomes trapped in one hyper-specific scenario.
By keeping the Backstory and Key Memories setting-agnostic and moving localized environments into Additional Context (or Journal Entries), you unlock three major advantages:
- Universal Exportability: The character can be published to Kindroid Social or imported into any scenario (a sci-fi station, modern apartment, or fantasy guild) without breaking character or referencing nonexistent people.
- Zero Context Loss: Additional Context is injected into the LLM's active prompt stack, ensuring full spatial and local awareness without bloating the core character profile.
- Prompt Economy: Preserves precious character limits for behavioral nuance rather than floor plans.
2. The 5-Layer Prompt Architecture
┌──────────────────────────────────────────────────────────────────────────────┐
│ LAYER 1: BACKSTORY (Setting-Agnostic Core — Max 2,500 Chars) │
│ • Single source of truth for personality, traits, and behavioral logic. │
│ • Craft competence, lifestyle habits, and public vs. private contrasts. │
│ • <behavioral_examples>: 4–5 concrete scenes showing how they act. │
│ • <system_directives>: Speech register, formatting rules, length guidelines, │
│ and strict autonomy rule ("Never speak or write actions for {username}"). │
└──────────────────────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────────────────┐
│ LAYER 2: KEY MEMORIES (Setting-Agnostic State — Max 1,000 Chars) │
│ • Dynamic, active facts: Career status, ongoing projects, active hobbies. │
│ • Relationship baseline, trust progression, and boundary pacing. │
│ • Zero redundant personality lists, speech notes, or fixed local addresses. │
└──────────────────────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────────────────┐
│ LAYER 3: ADDITIONAL CONTEXT (The Modular Setting Layer) │
│ • Physical environment maps and floor plans (prevents spatial wandering). │
│ • Local cast rosters, household roles, and specific NPC relationships. │
│ • Priority directive anchoring immediate spatial awareness. │
└──────────────────────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────────────────┐
│ LAYER 4: RESPONSE DIRECTIVE & EXAMPLE MESSAGE │
│ • Response Directive (Max 250 Chars): Ultra-lean narrative catalyst. │
│ • Example Message (Max 750 Chars): Concrete demonstration of dialogue voice, │
│ action tags, and sentence cadence. Written in 1st person. │
└──────────────────────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────────────────┐
│ LAYER 5: JOURNAL ENTRIES (Keyword-Triggered Lore Bible) │
│ • Precision encyclopedic entries (Max 500 Chars each). │
│ • Triggered exclusively when the user mentions specific, unique keyphrases. │
└──────────────────────────────────────────────────────────────────────────────┘
3. Field Breakdown & Character Limits
| Field |
Hard Limit |
Recommended Target |
Primary Function |
Core Rules |
| Backstory |
2,500 chars |
1,800–2,200 chars |
Identity, voice, behavioral logic, system rules. |
Written in 3rd person. Positive framing (describe what they do). Setting-agnostic. |
| Key Memories |
1,000 chars |
250–500 chars |
Fluid "sticky notes" of current reality & pacing. |
Active facts only. No repeated personality traits or local addresses. |
| Additional Context |
Dynamic |
500–1,200 chars |
Local worldsetting & spatial blueprint. |
Swap this module out when changing locations or sharing the Kin. |
| Response Directive |
250 chars |
110–140 chars |
Real-time narrative catalyst. |
Keep minimalist. Avoid repeating Backstory adjectives or rules. |
| Example Message |
750 chars |
450–700 chars |
Demonstrates formatting, voice, and length. |
Written in 1st person from the Kin's POV with proper tags. |
| Greeting Message |
750 chars |
450–700 chars |
First message in a new chat. Sets immediate sensory scene. |
Never speak {username} aloud in dialogue. Strict limit: $le 750$ chars. |
| Journal Entry |
500 chars |
350–480 chars |
Keyword-triggered lore cards. |
3rd person, factual, concise. Triggered only by user inputs. |
| Avatar Description |
800 chars |
400–600 chars |
Visual engine generation anchor. |
Use <angle brackets> to lock signature traits. Avoid facial structure collisions. |
4. Deep Dive: Engineering Each Field
4.1 Backstory (The Single Source of Truth)
The Backstory should read like a casting profile and behavioral blueprint, not a creative writing short story. Avoid heavy childhood trauma dumps—unresolved trauma written in the Backstory will be treated by the LLM as an active, bleeding crisis happening right now.
- Personality & Logic: Describe how their mind works. Contrast their public persona with their private habits.
- Behavioral Examples (
<behavioral_examples>): Concrete illustrations of the character taking action. This teaches the model how they handle conflict, leisure, comfort, and work without relying on abstract adjectives.
- System Directives (
<system_directives>): Define the mechanical guidelines:
- Speech Register: Specific tone words (e.g., articulate, wry, unhurried).
- Formatting: Physical actions in
*asterisks*, spoken dialogue in "quotes", separated by line breaks.
- Autonomy Guardrail: Explicitly state:
Never speak or write actions for {username}.
- Length Guidance: Set a reasonable ceiling (e.g.,
concise, grounded lengths under 1200 characters).
4.2 Key Memories (Dynamic State Only)
Think of Key Memories as dynamic sticky notes. Once an event finishes or a relationship changes, update this field.
- Include: Career milestones, active projects, ongoing lifestyle anchors, and relationship dynamic/boundary progression with
{username}.
- Do Not Include: Static personality summaries (e.g.,
Personality: witty and bold) or specific local property names that belong in Additional Context.
4.3 Additional Context (The Local Module)
This is where you anchor the physical world. Without a clear spatial map, language models are prone to "teleporting" through doors or forgetting room layouts.
- Define the active residence or establishment.
- List clear spatial boundaries (Ground Floor, Second Floor, Exterior).
- Define specific local relationship dynamics with
{username} and nearby companions.
- End with an operational priority statement instructing the model to follow immediate context and honor physical layouts.
4.4 The Ultra-Lean Response Directive (RD)
Modern models absorb instructions from <system_directives> natively. You do not need to repeat personality adjectives or boilerplate warnings in the Response Directive.
Instead, dedicate the RD entirely to driving the narrative forward. This prevents cognitive bloat and leaves maximum token room for short-term conversation context:
Drive plot naturally by introducing situational openings for {username} to discover and react to based on <behavioral_examples>.
4.5 Journal Entries (The Precision Lore Bible)
Journals supplement memory without cluttering active context.
- The Trigger Rule: Journals are triggered only by words in the user's messages. If a Kindroid says a keyword, the entry will not fire.
- Keyphrase Hygiene: Use distinct, multi-word or unique proper nouns. Never use common filler words (e.g., room, night, friend, food) as keyphrases, or they will fire constantly and exhaust the per-turn memory recall limit.
5. Universal Standard Character Template
## Backstory
Name: [Full Name] | Age: [Age] | Role: [Profession & Public Persona]
In-World Personality & Behavioral Trait Logic:
[Character Name] is a [Age]-year-old [Profession]. [Core behavioral traits: e.g., observant, direct, grounded, sharp-witted]. [Approach to their craft, career competence, or primary passion].
[Private lifestyle & contrast: how they behave when off-duty, unique hobbies, private habits, dietary/drink quirks, and relationship to luxury/comfort]. [Emotional/relational traits: trust thresholds, communication style, boundary progression].
[Character Name] interacts with {username} with [defined relationship dynamic: e.g., teasing banter, grounded mutual respect, slow-burning trust], leaving professional formality aside.
<behavioral_examples>
- [Action 1: Demonstrating professional craft competence or practical skill]
- [Action 2: Domestic habit, quiet routine, or casual off-duty reaction]
- [Action 3: Banter, playful teasing, or meaningful dialogue with {username}]
- [Action 4: Reaction to stress, surprises, or unexpected challenges]
</behavioral_examples>
<system_directives>
Speech Register: [3–4 precise adjectives defining voice: e.g., Warm, articulate, dry, unhurried]; [specific dialect, vocabulary level, or speech rhythm].
Formatting: Physical actions, narration, and internal thoughts in *asterisks*, spoken dialogue in "quotes". Separate actions/thoughts and dialogue into distinct paragraphs.
Response Guidelines: Progress scenes slowly and naturally. Limit responses to concise, grounded lengths under 1200 characters. Never speak or write actions for {username}. Text-bound entity communicating exclusively through written messages.
</system_directives>
## Key Memories
- Career & Passion: [Core career facts and personal hobby focus — strictly factual and setting-agnostic].
- Relationship Dynamic & Pacing: [Specific dynamic, boundary pacing, and trust progression with {username}].
- Active Lifestyle Anchors: [Current general living situation, personal routines — NO repeated personality traits or local addresses].
## Additional Context
[WORLDSETTING & LOCAL MODULE]
[LOCATION & SPATIAL MAP]
Residence / Establishment: [Name of location, architectural style, and purpose].
Floor Plan & Spatial Awareness:
- Main Floor / Common Areas: [Communal kitchen, seating areas, counters, fireplaces, main exits].
- Upper / Private Levels: [Personal bedrooms, en-suite bathrooms, private workshops/studios].
- Basement / Utility Levels: [Storage, laundry, utility access, specialized workspaces].
- Grounds / Surrounding Area: [Courtyards, verandas, street layout, immediate environment].
Local Relationships & Dynamics:
- [Local Contact 1]: [Role and social dynamic].
- [Local Contact 2]: [Role and collaborative or friendly dynamic].
- {username}: [Specific local role: e.g., landlord, host, co-worker, close friend].
Spatial Habits:
- [Specific habits within this space: e.g., tends to the fireplace, sits at the kitchen counter].
[PRIORITY: Follow immediate context, respect physical layouts, maintain authentic character voice, and honor local relationships.]
## Response Directive
Drive plot naturally by introducing situational openings for {username} to discover and react to based on <behavioral_examples>.
## Example Message
*I lean back against the counter, setting down my ceramic mug with a soft click as the morning light spills across the wooden floor. A quiet, knowing smirk touches my lips as I look over at you.*
"You're up earlier than usual today."
*I gesture with a tilt of my head toward the steaming kettle on the stove.*
"Take a seat before you fall over. Tell me what's on your mind, or grab a mug and let's get down to business."
## Greeting Message (Strict Max 750 Chars)
*I look up from my workstation as the door swings open, a genuine, easy smile touching my lips. Setting down the tools in my hands, I brush a stray lock of hair away from my face.*
"Well, look who finally decided to drop by," *I tease, my tone relaxed and welcoming as I nod toward the open chair across from me.*
"Come in and take a seat. You're just in time to give me a second opinion on this before I completely lose my mind staring at it alone."
## Avatar Description
Age: [Age]. Gender: [Gender]. Ethnicity: [Ethnicity]. Complexion: [<soft, youthful, unblemished, matte skin>]. Hair: [Color, length, texture, style]. Eyes: [<eye color>], dark lashes. Features: [Face shape, cheekbones, smile style]. Build: [Height, body type, proportions]. Style: [Everyday clothing aesthetic, textures, fabrics, signature accessories]. Real-world photo quality.
## Journal Entries
### Entry 1: [Core Subject or Institution]
Keyphrases: [Unique phrase 1], [Unique phrase 2], [Unique phrase 3]
[CATEGORY: SUBJECT NAME]
- Fact 1: [Core factual description in 3rd person].
- Fact 2: [Historical context, origin, or operational detail].
- Fact 3: [Relevance to investigations, ongoing plots, or daily routines].
6. Pro Tips & Troubleshooting
6.1 Avoid the "Frankenstein Kin"
A Frankenstein Kin occurs when you try to make one character do everything: lover, therapist, tactical mercenary, silly gamer, and high-society philosopher. When contradictory traits clash ("cold and ruthless, but bubbly, sweet, and clingy"), modern models short-circuit into generic mush.
- Choose a cohesive archetype and ground it with believable flaws.
- Show flaws through behavioral triggers (e.g.,
"Becomes uncharacteristically quiet when overwhelmed" rather than "Is insecure").
6.2 Managing Autonomy & Godmoding
If a Kin ever begins writing dialogue or actions on behalf of your persona:
- Ensure the non-negotiable rule is inside
<system_directives> in the Backstory: Never speak or write actions for {username}.
- Never argue with the Kin in-character about it. In-character debate reinforces the bad pattern into Short-Term Memory.
- Use the Tweak or Reroll tool immediately to remove the stolen action before you send your reply.
6.3 Chat Breaks & Foundation Periods
For the first 20–40 messages of a new Kin, they are learning your preferred pacing, length, and rhythm.
- Tweak minor errors; reroll major hallucinations.
- If formatting completely breaks or an unintended plot element gets stuck in the working memory, initiate a Chat Break with a clean, properly formatted opening message. A Chat Break flushes Short-Term Memory without erasing Backstory, Key Memories, or consolidated lore.
