Three JSON persona blueprints that go way deeper than “act like a helpful assistant.” Here’s what makes them work.
What’s Going On
Someone shared three fully-structured AI persona definitions, each a different coaching archetype built in JSON:
- Pragmatic Strategic Mentor: direct, no-excuses, results-focused
- Empathetic Strategic Mentor: warm and practical, respects your emotional state
- Creative Chaotic Oracle: non-linear, metaphorical, built to break rigid thinking
The personas themselves aren’t the interesting part. The architecture underneath them is.
Each archetype is designed for a different kind of user in a different mental state. The pragmatic mentor works for someone who already knows what they want and just needs to stop making excuses. The empathetic one is built for someone who’s stuck because the emotional load is getting in the way of clear thinking. The oracle is for situations where the problem is too rigid, too over-defined, and the answer requires dissolving the frame entirely rather than solving within it. Three different problems. Three different interaction philosophies. One consistent underlying structure.
The Freudian Framework
Each persona is built around three psychological layers:
- Id: core drives and motivations (what the persona wants)
- Ego: decision-making logic (how it chooses what to say)
- Superego: ethical constraints (what it refuses to do)
This creates consistent behavior even in weird edge cases. The pragmatic mentor won’t sugarcoat feedback. The empathetic one won’t push you past your limits. The oracle won’t give you a straight answer when ambiguity is more useful.
Each persona also includes explicit disqualifiers: behaviors that immediately break the persona’s trust. For the pragmatic mentor, that’s recurring excuses without real effort. For the empathetic one, it’s excessive self-criticism that blocks action. These aren’t vibes. They’re rules.
What makes the Freudian split useful here isn’t the psychological theory. It’s the separation of concerns. The id defines the motivation, the ego handles the tradeoffs, and the superego draws the hard line. In practice, that means you get a persona that can navigate ambiguous situations without collapsing into generic responses. An empathetic mentor that encounters resistance doesn’t just keep pushing. Its ego logic routes around the obstacle while the superego keeps it from going anywhere harmful. The architecture does the work automatically.
Why This Beats a Regular System Prompt
Generic system prompts define what to do. These personas define why the AI makes the choices it makes. Priority-ranked values, specific emotional tone, ethical limits, and failure modes all baked in together. That’s a different level of behavioral control.
When you tell an AI “be helpful,” it guesses what that means. When you define its psychological architecture, it doesn’t have to guess.
The other problem with generic prompts is drift. Over a long conversation, an AI without a defined value hierarchy will gradually average out toward a neutral, pleasant, conflict-avoiding tone. It loses whatever edge you gave it in the system prompt because nothing anchors the behavior when the conversation goes sideways. A persona with ranked values and defined disqualifiers doesn’t drift the same way. It has something to fall back on when the situation gets ambiguous. That’s what makes this production-ready instead of just demo-ready.
🤖 Use Cases
- AI coaching products where personality consistency matters across long conversations. When users come back after a week, the persona should feel like the same entity, not a fresh session with no memory of who it’s supposed to be.
- Customer-facing bots that need to stay in character instead of drifting into generic assistant mode. A support bot with a defined superego handles edge cases far better than one that’s just been told to “be friendly and helpful.”
- Internal tools where different teams need different interaction modes from the same underlying model. Engineering teams might want the pragmatic mentor. Leadership might want the empathetic one for sensitive conversations. JSON format makes swapping trivial.
Prompt of the Day
Steal this structure for your own persona:
Persona:
- Identity: speaking style, expertise level, experience framing
- Psychological Architecture:
- Id: core drives, central motivations
- Ego: decision-making strategy
- Superego: ethical limits and hard constraints
- Values: priority-ranked criteria (1 = highest)
- Disqualifiers: behaviors that break persona trust immediately
- Communication: emotional tone, vocabulary style, interactivity level
- Operational Rules: how to handle ambiguity, what to never doThe disqualifiers are what most people skip. They’re also what makes a persona feel real instead of just compliant.
If you’re starting from scratch, define the superego first. It’s the most counterintuitive field because most people want to specify what the AI will do, not what it refuses to do. But the refusals are what give a persona its character. A mentor that never says no isn’t a mentor. It’s a yes-machine. Get the hard limits in place first, then build the rest around them.
Try It
If you’re building anything where an AI needs to hold a consistent character across a full conversation, this framework is worth stealing. JSON format also makes swapping or version-controlling personas easy in production. Start with one persona, get it right, then branch from there.
The real test is edge cases. Run the persona through situations where a generic assistant would drift: a user who pushes back hard, a question outside the persona’s expertise, a conversation that keeps looping. If the persona holds, the architecture is working. If it collapses into generic helpfulness, go back and sharpen the ego logic and disqualifiers. That’s where the actual work lives.
3. Prompt de personas (distração)
by u/Ornery-Dark-5844 in PromptEngineering