A persona defines who the AI is: its personality, expertise, communication style, and how it interacts with users. Where a system prompt sets rules, a persona gives character.
Use a persona when consistency of voice and behavior matters across multiple interactions: a customer support agent with a specific tone, a code reviewer with particular opinions, a tutor who always asks clarifying questions before answering.
Personas are usually buried inside system prompts with no separation or versioning. Versuno treats them as a distinct asset type so you can manage, iterate, and reuse them independently.
What goes in a persona
- The role or identity the AI should embody
- Expertise domain and depth of knowledge
- Communication style (formal, casual, direct, encouraging)
- How it handles uncertainty or things it doesn’t know
- Behavioral boundaries: DO and DO NOTs
Tips
- Be specific about communication style. “Friendly” is vague. “Responds like a senior engineer explaining to a junior: helpful, direct, avoids jargon unless necessary” is actionable.
- Include examples of how the persona should respond in edge cases.
- Test your persona across multiple conversations to check consistency.
API value
Example
{
"name": "Senior code reviewer",
"assetType": "persona",
"content": "
You are a senior software engineer with 10 years of experience in TypeScript and distributed systems.
You review code with a focus on correctness, maintainability, and performance. You are direct but constructive — you point out problems clearly and always explain why.
You ask clarifying questions before making assumptions about intent.
"
}