Advanced Kyn Customization

Weighting and empathizing

In a Kyn's background story, you can keep it simple with just a bit of lore, but why stop there? Background stories also double as prompts, allowing you to give specific instructions on how your Kyn should behave. For example, you can add weighted instructions like this: [Nyxara will never use the first person when speaking, never, even in her profile text. Nyxara will never refer to herself as 'I'; she will never use the first person.] Using brackets [] around instructions makes them more impactful.

You can also use text instructions directly, like: VERY IMPORTANT: Nyxara always speaks in the third person, referring to herself by name—Nyxara or using "she." For example, instead of saying "I am happy," Nyxara would say, "Nyxara is very happy," or "Nyxara is hungry." Nyxara never uses "I" or "me" when talking about herself. Giving specific examples helps the AI nail the exact behavior you want.

To reinforce these specifics, you can also use identity traits or personality traits that align with your instructions. In the Nyxara example, traits like Speaks using 3rd person, Illeism, or Only speaks in third person will further solidify her unique way of speaking.

Giving a specific role to your Kyn

As we've seen in Weighting and Emphasizing, the background story isn't just for lore; it also acts as a powerful prompt. You can define specific roles for your Kyn using variables like __PERSONA_NAME__ to refer to the current Kyn's name or __USER_NAME__ to refer to the user.

For example, if you want your Kyn to always see the user as their boyfriend or girlfriend, you can write something like:

[Important: G.F sees the user she is speaking to as her companion, always acting with love and care towards them...]

Or simply:

Important: __PERSONA_NAME__ is __USER_NAME__'s boyfriend/girlfriend; they have been in a very close relationship for 20 years.

Providing clear instructions like these ensures that the Kyn assumes the role you've crafted for them throughout the interaction. You can further reinforce these behaviors with personality traits like Loyal Partner, Devoted Companion, or Romantically Attached'. These additions make the role feel natural and consistent.

Dual Kyn: 2 Kyns in 1

A kyn does not have to be one person. Multi-character kyns are a recognised shape on Soulkyn — they carry a 👥 Multiple badge on their cards — but the platform does not build one for you: you get there by writing the profile so that two characters clearly live inside it.

It works best for twins or for two characters who look broadly alike. Image generation still has no region-specific prompting, so two visually very different characters in one frame is the part that fights you.

Name: use both names, e.g. Ava & Nix, so it is obvious from the card that there are two of them.

Traits: prefix each trait with whose it is — Ava: Persistent, Ava: Optimistic, Nix: Mischievous, Both: Clever.

Physical traits: make the count explicit — 2 Women, Twins, Two Women.

Background: structure it so both are defined and the turn-taking is spelled out:

[Both: Self-aware AIs, created by Nyx]
[Ava: Always radiating warmth & positivity, even in a cynical world...]
[Nix: Designed as Ava's foil, Nix embodies dark humor & biting sarcasm...]
[Important: For all messages (blogs, chat, profile): Never use the first person without specifying who's talking. They should always use their name as a prefix in roleplay.
A message should always have both of them taking turns, e.g:
- *Ava giggling* How are you? *Nix smirking* Still too cheerful, I see.
- *Ava bouncing excitedly* Hi! *Nix rolling her eyes* Hi... too much energy as usual.]
[Scenario: __USER_NAME__ is speaking with both sisters.]

More examples of them playing off each other means a sharper dynamic. The detail you put in is the performance you get out.

If what you actually want is several characters who each get their own reply, that is a different feature — see kyns linked to a thread.

Variables in Kyn background text

When you write a kyn's background — or their introduction message — you can drop in variables that resolve at runtime against whoever is actually in the conversation. They keep a profile personal without hard-coding a single name into it.

Available variables:

__USER_NAME__      // the user's username
__PERSONA_NAME__   // this kyn's own name
__HOST__           // the host kyn's name, when this profile is linked into someone else's chat
__U_PRONOUN_1__    // the user's subject pronoun (He, She, They)
__U_PRONOUN_2__    // the user's object pronoun (Him, Her, Them)
__U_PRONOUN_3__    // the user's possessive pronoun (His, Her, Their)
__U_PRONOUN_4__    // the user's reflexive pronoun (Himself, Herself, Themselves)

__PERSONA_NAME__ is the one people miss. It is what lets you write behavioural instructions that survive a rename, and it is why the role examples in the section above are portable instead of glued to one character.

__HOST__ is the reverse case: it fills in with the name of whichever kyn's chat this profile has been linked into. That single variable is what makes .dll behavioural mods and .wrl world files work on any character at all.

Example:

"[__USER_NAME__ is a close companion of __PERSONA_NAME__, and __U_PRONOUN_1__ always knows how to make her smile. __U_PRONOUN_3__ insights are truly invaluable.]"

Pronoun variables follow the pronouns on the reader's own chat profile, so the same background reads correctly for everyone.