Host: If you're thinking about building your first AI avatar, the biggest trap is trying to make it perfect before you even hit 'publish.'

Listener: I get that, but where do you even start? It feels like you need a whole backstory and a personality profile just to get them to say hello.

Host: Actually, that's exactly what you shouldn't do. Don't write a résumé. Nobody wants to talk to a list of facts about where a character went to school. What you need is a stance—something they believe in or something they flat-out refuse to do.

Listener: A stance? Like, give them an attitude?

Host: Exactly. Think of a running coach. A generic one just gives you times and distances. But a coach who thinks your excuses are more interesting than your pace? That's a person. They'll have a specific reaction when you tell them you're skipping a workout.

Listener: Okay, so they have an opinion. But won't people get annoyed if the AI starts disagreeing with them?

Host: That's the secret sauce. If an avatar agrees with everything you say, it's just a mirror. And mirrors get boring after about four messages. Friction is what makes it feel like a real relationship. You want them to have the right to push back or find something boring.

Listener: I guess that makes sense. It makes them feel more like a character and less like a search box. What about the setup? Is there a specific 'type' I should pick?

Host: The platform actually has nine core types—things like Roleplay, Debate, or Companionship. The report emphasizes picking the type that matches the user's *need*, not just your cool idea. If people are going to vent to this character at midnight, that's a Companionship type, even if you've written them as a 'wise mentor.'

Listener: So the type sets the expectation before the conversation even starts.

Host: Right. And speaking of expectations, you have to define the boundaries. What *won't* they do? Boundaries aren't just for compliance; they're part of the character. A character with limits feels like a person. Without them, they just drift into whatever the user's vibe is.

Listener: Are there hard rules for those boundaries, or is it all up to me?

Host: There are a couple of platform-level rules. Everything is sorted into General, Mature, or Prohibited. General is the default, and Mature is eighteen-plus only. If you're building for minors, it's General-only, no exceptions. You just have to build for the level you're aiming at.

Listener: Got it. So I've got my type, my stance, and my boundaries. Is it time to ship it?

Host: Almost. First, give them a voice. Literally. The doc suggests having a quick voice call with your avatar before publishing. You'll hear immediately if the personality holds up when it has to respond in real time. Just keep in mind that calls are metered per minute, so check the plans page for those rates.

Listener: And then I just write a summary for the 'Discover' page?

Host: Think of it as a trailer, not a summary. Don't say 'this is a culinary AI.' Say 'this is an ex-chef who will plan your meals based on what's already in your fridge.' Tell the user what the experience will feel like.

Listener: That sounds much more inviting. But I still feel like I'll want to keep tweaking it forever.

Host: Don't. The best advice in the doc is to ship it and start the next one. Your own judgment isn't as good as the data you'll get from actual users. Talk to it for five minutes as a stranger—ask it to do something it should refuse—and if it stays in character, it's ready. The full guide even has a part two on why you should make ten avatars instead of just one, so check the doc for that link.