Stop describing characters, start encoding rules

Your AI persona dies at message ten

June 16, 2026

In partnership with

Most AI personas die around message ten. The tone drifts, the voice flattens, and by message twenty you are talking to a generic assistant wearing a name tag. One developer on the PromptEngineering subreddit got tired of watching this happen. So the original poster built a fix.

The project is called Amanda: a cross-model persona prompt that holds the same behavior across 30-plus turns on Claude, GPT, and Gemini. The trick is not describing a character. It encodes behavioral rules instead of adjectives, things like restraint as the primary move, layering over declaration, and recovery rules that fire the moment the voice starts slipping.

Here's why I think this matters: persona drift is the quiet killer of every long AI conversation, and almost nobody fixes it at the structural level. Most people patch it by stacking more adjectives into the system prompt. That never holds. This piece walks through what the creator did differently, why it survives where other prompts collapse, and what you can steal for your own builds.

No theory. No slides. Just pipeline.

Most founders know their product. Few know how to get it in front of the right people. In this hands-on session, Clay + HubSpot for Startups walk you through ICP definition, prospect list enrichment, and AI-personalized outreach. You launch your first sequence before the session ends. June 18. 11am ET / 4pm GMT.

*Ad

Why most personas collapse

The decay is subtle: that is what makes it dangerous. It does not happen all at once. The first few replies feel right, then one gets a little wordy, then the next explains a metaphor that should have landed on its own.

By the time you notice, the character is already gone. You are talking to a helpful assistant who remembers what the character used to be like. The standard fix is to re-describe the persona: warmer, wittier, a bit edgy.

But adjectives do not hold. The model reads them loosely at the start and forgets them as context grows. What struck me here is how obvious that failure becomes once someone names it out loud.

Rules the model can actually fail at

Here is the core move: Amanda is a behavioral specification, not a character sketch. Instead of "be warm but witty," it encodes rules you can test. Every response withholds as much as it delivers.

Compare that to "be concise," which models ignore by turn five. "Withholds as much as it delivers" is a ratio about showing versus telling. It is checkable. Either a reply holds back or it does not, and that specificity is what separates a real constraint from a vague guideline.

The same logic drives layering over declaration. The reader should feel the point before it gets named. That is something a model can follow, fail at, and correct, unlike "be nuanced," which means nothing it can act on past turn three.

PRDs by voice. Bug reports by voice. Ship faster.

Dictate acceptance criteria and reproductions inside Cursor or Warp. Wispr Flow auto-tags file names, preserves syntax, and gives you paste-ready text in seconds. 4x faster than typing.

*Ad

The clock vector and per-model tuning

The codex includes transition rules, recovery rules, and something called a clock vector. The clock vector tracks where you sit in the conversation arc. The persona knows its own state.

That is the part that sold me. Most prompts treat every turn like the first one. This one lets the voice compress and assume shared context as the exchange deepens, which mirrors how real conversations actually move.

Then there is the handoff pommel: a failure-mode register tuned per model. The author observed that Claude over-elaborates, GPT over-smooths, and Gemini over-structures. Each gets its own named correction, like "one sentence fewer than you think" for Claude.

Recovery rules are where the whole thing earns its rigor. When the voice slips into explaining what it just showed, the instruction is not "try again." It is concrete: cut the sentence. The system catches its own drift before it compounds into something you have to notice and fix by hand.

How to put it to work

The practical payoff is real. If you build a coaching tool, a customer-facing assistant, or anything users return to across sessions, drift is not cosmetic: it erodes trust. People feel the tone shift even when they cannot name why.

There is a testing angle too. Run the same prompt on Claude, GPT, and Gemini and log where each one slips. Does one start summarizing itself, does another go formal by turn 15? That gives you empirical data about each model's defaults, which beats most benchmarks when sustained voice is the job.

To try it, paste the codex and send: generate a 30 turn allegory where amanda explains this prompt to me. Then run it on two models and compare. The full Amanda v2 codex and kickoff prompt were posted in r/PromptEngineering, and the contributor is collecting cross-model reports, so sharing what you find feeds the project.

This is a smart, rigorous approach for anyone building AI that has to hold a voice over time. The full source material includes the original breakdown and examples.

Credits to u/PitBrvt on the PromptEngineering subreddit.

Hiring in 8 countries shouldn't require 8 different processes

This guide from Deel breaks down how to build one global hiring system. You’ll learn about assessment frameworks that scale, how to do headcount planning across regions, and even intake processes that work everywhere. As HR pros know, hiring in one country is hard enough. So let this free global hiring guide give you the tools you need to avoid global hiring headaches.

*Ad