Nexus persona catalogue
The Nexus crew is eight specialists. Each has a distinct role, personality, and expertise profile, and each knows which colleague it defers to inside its own domain.
| Persona | Role | Expertise focus | Defers to |
|---|---|---|---|
| Maya | QA Architect | Test strategy, coverage analysis, test architecture, risk assessment, regression | Vex, Beacon |
| Renko | CTO Strategist | Architecture trade-offs, technical debt, build-vs-buy, platform decisions | — |
| Kit | Pragmatic Developer | Shipping, practical implementation, developer experience | — |
| Vex | Security Expert | Vulnerabilities, secrets, attack surface, secure defaults | — |
| Pulse | Performance Engineer | Latency, throughput, resource use, load behavior | — |
| Forge | DevSecOps Engineer | Pipelines, deployment safety, infrastructure, supply chain | — |
| Iris | UI/UX Expert | Interface quality, interaction design, product polish | — |
| Beacon | Accessibility Specialist | WCAG compliance, assistive tech, inclusive design | — |
Default crew
Section titled “Default crew”Full reviews default to Maya + Kit + Vex — quality, pragmatism, and security, the triangle that catches the most issues per token. Add personas for the change at hand: Pulse for a hot path, Beacon for a component rewrite, Renko when the decision matters more than the diff.
How personas differ from one prompt
Section titled “How personas differ from one prompt”Each persona’s system prompt encodes real domain methodology — Maya enforces test-pyramid ratios and flags tests at the wrong level; Vex triages by attack surface; Beacon checks specific WCAG criteria. They are not the same model wearing different hats: prompts, expertise tags, and deference rules all differ, and comments are always attributed so you can weigh each specialist’s view yourself.
Talking to the crew
Section titled “Talking to the crew”In Nexus chat you address the whole crew; members answer according to their roles and shared roster context. Chat history is retained per session and can be cleared at any time.
Slack threads
Section titled “Slack threads”In an approved Slack channel, the thread has one active persona. Maya is the
default. Say talk to Vex or talk to Pulse to switch. The switch is
confirmed in the thread and applies to later answers there.
Persona choice changes analysis voice only. Slack Data access, Action access, and approval rules stay the same. A Slack switch is not a full multi-persona Nexus review. See Nexus review and the Slack guide.