Tab · Product
Personas
Build for the right user, not the abstract average — every feature decision starts here. Three primary personas (Vince the vibe coder · Eng manager Eve · Solo founder Sam), each with goals, frustrations, and the surfaces they actually live in. Lives at .claude/brain/personas.md.
See it in motion
Where to find it
- Localhost:
/personas.html?repo=<id> - On disk:
.claude/brain/personas.md - Keyboard: ⌘ K then
personas - Sidebar: Product → Personas
What it does for you
A named user behind every feature.Vince ships a side project in a weekend. Eve runs a team of seven. Sam is paying rent with one repo. Every roadmap row should make at least one of them visibly happier — if it doesn't, ask why it's on the list.
Settles UX debates fast.Two designers, one button. Which persona is this for? The answer is usually obvious once asked. Personas turn taste arguments into evidence arguments.
Updated when the user changes, not when convenient.When real usage shows a persona is wrong (or a new one is emerging), the file gets edited in the same PR as the feature that surfaced it. Personas decay if you let them.
Configure
Nothing — hand-edit the markdown. Three personas is the cap; if you need a fourth, retire one or merge two. More than three and nobody remembers them.
Use it well
Open Personas before opening a roadmap row. State which persona benefits and how the surface they live in changes. If a feature serves all three equally, it's probably plumbing — write that explicitly so it doesn't get over-designed for one of them.