Goony.ai —

How to write a character card that roleplays well

Write a character card that stays in character: description, personality, scenario, first message and example dialogue, plus lengths, tokens and mistakes.

Updated Nov 2, 2026 · 9 min read

In this article
  1. Start with one sentence
  2. Step 1: The description
  3. Step 2: The personality
  4. Step 3: The scenario
  5. Step 4: The first message
  6. Step 5: Example dialogue
  7. Step 6: The parts that aren't for the model
  8. How long should a character card be?
  9. Common mistakes
  10. Writing a character in Goony's creator
  11. A last check before you share it
  12. FAQ

A character card that roleplays well does three jobs: it tells the model who the character is (description and personality), where the story starts (scenario and first message), and how they talk (example dialogue). Write the first message the way you want every reply to read, keep the always-sent part short enough to leave room for the chat, and show traits through what the character does and says instead of stacking adjectives.

This guide works for any app that reads cards, from SillyTavern to Chub to Goony's own creator. Every character you write should be an adult, and the card should say so: state an age of 18 or over and write them as a grown-up. Most platforms require it, Goony included.

If you're new to the format, our explainer on what a character card is covers every field. Here we focus on writing them.

Start with one sentence

Before any field, write the concept in a line: who they are, what they want, and what's in the way. For example: Wren Ashdown, 29, a ranger who guards a mountain pass and doesn't trust travelers, owes you her life after an avalanche. If you can't say it in one line, the card will wander. Everything below is that sentence, unpacked.

Step 1: The description

The description is sent to the model with every reply, so it holds everything that must always be true. SillyTavern's character design docs put it simply: "all important facts should be included here."

What belongs here:

  • Identity: name, age (18 or over), role, the one or two physical details that matter in scenes.
  • History: three or four facts that explain how they act now, not a biography.
  • Wants and fears: what they're after, and what would make them back off.
  • How they treat you: the relationship at the start, and how it can change.
  • Speech: formal or blunt, sentence length, a habit or two.

Lead with the most important facts. If something only matters some of the time (a rival guild, the layout of a castle), it belongs in a lorebook entry, not the description.

On format: Chub's own character creation guide says plain text is recommended. Community formats exist (W++, bracketed lists, PList with example-based styles), and SillyTavern's docs call formatting "a complicated topic" and link to community guides. Plain prose works everywhere and reads cleanly when you edit it later.

Step 2: The personality

Keep it to a line or two, and make it about behavior. "Brave, kind, stubborn" tells the model nothing it can act on. Compare: Says she isn't tired, then falls asleep on watch. Will share her last ration and complain about it the whole time. Behavior gives the model something to write; adjectives give it a mood to guess at.

Many good cards skip this field and fold personality into the description. Chub's editor does the same: its guide treats personality as part of the description.

Step 3: The scenario

The scenario sets the scene: where, when, and what's happening between the character and you. One short paragraph. Name the place, the situation and the tension, then stop. Don't decide what you, the user, will do or feel; leave that to the chat.

A mountain hut on the Greyfell pass, the night after the avalanche. Wren dug you out of the snow and dragged you here. The storm has closed the road for two days.

Step 4: The first message

The first message matters more than its length suggests, because the model copies it. SillyTavern's docs note that the model tends to mirror the first message's style and length, so it's "important to write it in a way that you want the responses to be." If you want long, descriptive replies, write a long, descriptive opener. If you want quick back-and-forth, keep it short.

Three rules:

  1. Never speak or act for the user. Describe the character and the world, then hand the turn over.
  2. End on an opening: a question, a choice, or something that demands a reaction.
  3. Match the format you want back. If you put actions in asterisks and dialogue in quotes, the replies will too.

Wren drops another log on the fire without looking at you. "You're awake. Good. You snore like a rockslide." She tosses a dry shirt onto your blanket. "Road's closed for two days. So, traveler, what were you doing on my pass in a storm?"

Write one or two alternate greetings too. They're extra openers you can swipe between, and they let the same character start in a different mood or place.

Step 5: Example dialogue

Example messages teach the voice: word choice, rhythm, how much the character says per turn. Each example block starts with <START>, and lines begin with {{user}}: or {{char}}:, placeholders the app fills with your name and the character's.

<START>

{{user}}: Why do you stay up here alone?

{{char}}: Wren shrugs, eyes on the fire. "The pass doesn't lie to me. People do." A beat. "You're not people yet. Don't ruin it."

Two or three short exchanges are usually enough. Pick moments that show something the description can't: how the character deflects, jokes, or softens. Keep in mind that examples are the first thing to go when the chat gets long: SillyTavern drops them "block by block" as the chat history fills the context, so the description has to stand on its own.

Step 6: The parts that aren't for the model

  • Creator notes are for people reading the card. The V2 spec says they "MUST NOT be used inside prompts," so put tips here ("works best with a slow start"), not instructions.
  • Tags help people find the card. On Chub, "characters with less than three tags will be hidden in search."
  • System prompt and post-history instructions override the app's own settings in apps that support them. Leave them empty unless you know why you need them.

How long should a character card be?

Short enough that the always-sent fields leave most of the context for the conversation. SillyTavern's docs give the example that with a 2,048-token context, "a 1000-token character definition cuts the AI's 'memory' in half," and its token counter turns red when a definition uses more than half of the context. Context sizes vary a lot between services: JanitorAI's free model has "around 9k tokens," and SpicyChat's free tier caps context at 4,096 tokens (both per their own docs, October 2026).

Our rules of thumb (a token is roughly three-quarters of an English word):

Field Suggested length Why
Description 150–500 words Sent every reply; the core of the character
Personality 1–2 sentences Often redundant with the description
Scenario 2–4 sentences Sets the scene, then gets out of the way
First message As long as you want replies to be The model copies it
Example dialogue 2–3 short exchanges Dropped first when the chat grows
Lorebook entries A few sentences each Only added when their keyword comes up

Some platforms set hard limits instead: Goony's character prompt, for example, holds up to 4,000 characters.

Common mistakes

  • Writing for the user. "You feel a chill as you step inside" in a greeting takes the user's turn. Describe the room; let them decide how it feels.
  • Contradictions. "Shy and reserved" in the personality, a flirt in every example. The model will pick one at random.
  • Adjective soup. A list of twenty traits blurs into nothing. Five specific behaviors beat twenty adjectives.
  • Lore dumps. A page of world history in the description crowds out the conversation. Move it to a lorebook.
  • A first message you don't like the style of. Rewrite it until it reads exactly like the replies you want.
  • No stated age, or a vague one. State an adult age plainly. Several sites prohibit characters whose age is ambiguous, and an adult character should read as one.
  • Real people. Many platforms restrict characters based on real people, and Goony doesn't allow them at all. Write fiction.

Writing a character in Goony's creator

Goony's character creator uses its own fields rather than the raw card format, and the same principles apply:

  • Name, tagline, gender and style (anime or realistic), plus a portrait you upload.
  • A structured sheet: age (18 or over), body type, ethnicity, language, relationship, occupation, hobbies and personality.
  • A character prompt of up to 4,000 characters. This is your description, personality, scenario and example lines in one place.
  • Up to five opening scenarios, Goony's version of the first message and alternate greetings.
  • An NSFW toggle. Characters are always 18+.
  • Improve with AI, which rewrites your prompt into a polished version. It sends your fields to Goony's server to do that.

The creator saves the character in your browser and needs no account, so you can draft freely; chatting with it needs a free account. You can sync it to your account later, or submit it for publication, which is reviewed. Characters you create or import locally, and your Offline chats, live in your browser, not in Goony's database. Each reply is still generated on Goony's servers.

If you'd rather write in a card editor, publish the card publicly on Chub and bring it into Goony by link: our guide to importing a character card has the steps. For inspiration, look at Goony's hand-made cast: Sylvaine, an elven ranger, and Kael, a demon prince, each start from a one-line hook.

A last check before you share it

  1. Does the one-line concept still describe the card?
  2. Is the age stated, and is it 18 or over?
  3. Does the first message avoid acting for the user, and end on an opening?
  4. Do the examples sound like the same person as the description?
  5. Is anything in the description only relevant sometimes? Move it to the lorebook.
  6. Did you chat with it for twenty messages and fix what drifted?

If you save the card as a PNG to share, keep a JSON copy too: image compression can strip the data, as our guide to a card PNG that won't import explains.

FAQ

How long should a character card be?

Keep the description to a few hundred words and the always-sent fields well under half of the model's context. Two or three short example exchanges and a first message as long as the replies you want are enough for most characters.

Should I use W++ or plain prose?

Plain prose is the safest default. Chub's guide recommends plain text, every model reads it, and it's easier to edit. List formats can save tokens but are harder to keep consistent.

What do the char and user placeholders do?

They stand in for the character's name and the name of whoever is chatting. The app swaps them in, so the card keeps working if you rename the character or someone else uses it.

Do example messages really matter?

Yes, especially early in a chat. They teach the voice and reply length. They drop out as the conversation grows, so the description has to carry the character on its own.

Can I write a character without an account?

Yes. Card editors like SillyTavern run without one, and Goony's creator saves characters in your browser with no account. You'll need a free account to chat with your character on Goony.

What's the minimum age for a character?

  1. Goony requires every character to be an adult, and most roleplay platforms have the same rule. State the age in the card.

Characters to try

Try Goony.ai

Chat with any character for free — 20 messages a day, no card needed. Create your own or import one from the community.

Keep reading