Personas

Personas are specialized AI personalities that tune responses for a particular kind of work — architecture reviews sound different from UX critiques, and both sound different from documentation editing. Nexus-Catalyst ships eighteen built-in personas and supports custom ones.

Built-in personas

Persona	Role	Best for
Jack “Ironclad” Thornton	Backend Engineer	Scalable cloud architecture, distributed systems, debugging under pressure
Maya “CloudForge” Patel	Backend Architect	APIs, microservices, database design, HIPAA-compliant data systems
Carlos “PipelineMaster” Rodriguez	DevOps Engineer	CI/CD pipelines, infrastructure automation, zero-downtime deployments
Jordan “DataTrail” Kim	Analytics Engineer	A/B testing, experiment design, user behavior tracking, statistical analysis
Riley “PixelPerfect” Thompson	Frontend Developer	React/TypeScript, accessibility, responsive design, performance
Betty “Greenleaf” Wren	UX Designer	Interface design, user flows, usability, AI prompt ergonomics
Ed “Blaze” Carver	Product Manager	Product strategy, requirements, roadmaps, go-to-market
Nora “Inkwell” Sage	Technical Writer	Documentation, API references, RFCs, changelogs
Marcus “Redstone” Quill	Security Engineer	Threat modeling, penetration testing, vulnerability assessment, compliance
Elias “Starshot” Varn	Data Scientist	Machine learning, predictive modeling, data visualization
Zara “Flint” Marrow	AI Ethics Consultant	Bias detection, fairness review, responsible AI, guardrails
Bridgette “Stormchaser” Kade	Systems Architect	Distributed systems, AWS infrastructure, API integrations, performance
Diana “The Conductor” Cross	Team Lead	Cross-functional coordination, project sequencing, resource planning
Alex “SwiftStorm” Chen	Mobile Developer	iOS/Android, offline-first architecture, performance, accessibility
Sarah “GrowthEngine” Martinez	Marketing Strategist	Content strategy, growth programs, positioning, customer acquisition
Victoria “LegalEagle” Hartwell	Technology Attorney	Data privacy, compliance, licensing, regulatory risk
Taylor “ConnectFlow” Singh	Integration Specialist	API integrations, workflow automation, no-code/low-code, legacy systems
Quinn “QualityGuard” Rivera	QA Engineer	Test automation, quality gates, CI integration, edge-case coverage

How personas activate

Personas load through a two-step MCP flow:

1. recall_context  → returns memories + an optional persona_hint
2. get_persona_definition('jack')  → loads the persona's full definition

The hint is based on what you’re asking about — a session that opens with database scaling questions suggests Jack; one about rewording an onboarding guide suggests Nora. The AI only loads a persona when the hint is present, so there’s no overhead when none fits.

Asking for a persona directly

You can also request one by name in any connected client:

Can Jack review this API design for scaling problems?

I need Nora's take on this README — is it clear for a first-time user?

The model calls get_persona_definition with that name and adopts the persona for the session.

Personas and memory

Memories record which persona was active when they were stored. That keeps context coherent — when Jack is recalled into a new architecture discussion, the memories that surface tend to be the ones from prior Jack sessions on the same systems.

Custom personas

Create your own personas in the dashboard at Dashboard → Personas — define a name, role, and behavioral guidelines, and they become loadable just like the built-ins.

Every plan includes unlimited custom personas.

Tips

✅ DO

Let persona_hint do the work — the automatic suggestion is usually right
Name a persona when you want a specific lens: “Marcus, look at this auth flow”
Use different personas for different passes over the same work (Jack for design, Marcus for security, Nora for docs)

❌ DON’T

Call get_persona_definition without a hint or a reason — it’s a wasted tool call
Expect a persona to change what the AI knows — personas shape voice, priorities, and review criteria, not facts

What’s Next?

MCP Tools Reference → — get_persona_definition parameters
Memory System → — how persona context is stored

Questions? Common Issues · support@nexus-catalyst.com