A profile provides direction, not a locked script. See how appearance, personality, relationship, memory and voice work together, then adjust what does not fit the role or your needs.

Nastia sound description
Describe the age impression, rhythm, warmth, texture and delivery you want to hear. A focused note can guide the voice while leaving room for variation between messages.
Nastia trait controls
The companion editor displays Passion, Wit, Warmth, Boldness, Loyalty and Charm. Relationship and romance options add context, making personality choices easier to compare before a deep roleplay begins.
Nastia long-term recall
Memory is designed to bring useful details from earlier conversations into later ones. It may miss something, confuse importance or retrieve the wrong note. You can correct direction instead of assuming all history will appear perfectly.

Nastia appearance references
Set an avatar, crop the image and attach face or body references to visual prompts. A portrait already created in the gallery can become a reference when the same character moves into another location, outfit or style.
Nastia response controls
Edit, delete, reroll or expand a message when the conversation goes off course. Bubble density, chat backgrounds and image fit settings change the interface around the exchange, but decoration alone does not make a weak response engaging.
✺ ✺ ✺
Nastia check-ins
A companion may send a follow-up after you have been away. Check-ins can be switched off, so reaching out remains optional. The user chooses whether a character waits quietly or continues later.

Nastia image awareness
Vision allows a companion to inspect an uploaded picture and answer in character. This can support a captioned photograph, a contextual response, a related image prompt or a video idea without pretending the model sees more than the file contains.
Nastia backstory foundation
Backstory explains who the companion is, how you know each other and which events matter. Specific facts usually work better than a biography filled only to reach the limit. Keep the full version when complexity serves the scenario; use less when the role is simple.