Generating personas
On this page
Generating personas
The people you're building for, created from your project summary and refined one at a time.
Personas give every feature, story and page a real person to design for. You don't have to generate them: as soon as your project summary names its user roles, VibeMap creates one persona per role for you. Personas live on the Features page, on the Personas tab and on the Map.
Figure: The Personas tab on the Features page.
Where your personas come from
When your summary is ready, open Features. VibeMap adds a light baseline persona for every user role the summary lists: a name, a one-line tagline, an avatar and the role. Baseline personas are free and enough for features, stories and permissions to reference.
Add a role to your summary later and its baseline persona appears the next time you open Features. Nothing is regenerated or overwritten.
Finding them
- Personas tab (
Features → Personas): every persona, grouped by role. This is where you review, add and edit. - Map tab (
Features → Map): personas sit on the canvas next to the stories they act in and the pages they can use. Click a persona to open it in the side panel.
Working with a persona
Everything happens one persona at a time. There is no "generate all" button.
- Generate details: on a baseline persona, fills in the full profile: demographics, behaviour, goals and motivations, pain points and a short narrative. It rewrites only that persona.
- Regenerate: on a detailed persona, redraws its profile. The persona keeps its role, so stories and permissions stay linked.
- Add persona: creates one new persona. Pick a role (an existing one or a new one) and the AI writes the rest.
- Edit inline: click any field to change it. Your edits save as you go and are versioned, so you can always undo.
- Delete: removes the persona. Stories that named it keep their role.
- Export JSON: the Map toolbar's JSON button copies or downloads what the Map is showing. Show only personas to export just them, handy for a research doc or another tool.
⚠️ Watch out: user stories and access rules key off a persona's role. Renaming a role changes what every story and permission points at, so rename deliberately.
Needs attention
The Needs attention chip on the Personas tab and the Map counts issues with your personas and their roles, for example the same role spelled two ways. Open it to see each reason and its fixes. On the Map, Show keeps the affected personas bright and fades the rest.
A reason that doesn't point at anything on the Map still appears in the attention chip's counts and fixes, but its Show is greyed out, because there is nothing on the Map to highlight. (Everything greys out too when no reason can be shown.)
With the agent
In the agent, type /gen-personas to add one persona, optionally saying who it is: /gen-personas a dive centre owner who books group trips. On a project with no personas yet, the agent suggests Create personas from roles, which creates the baseline set.
⚡ Power-user hints
- Goals and pain points do the heavy lifting. They are the fields the feature and story generators lean on most. Generate details for the personas your MVP serves first.
- Fix the roles in your summary, not in the personas. The summary's user roles are the source of the baseline set.
- Feed real research back in. If you have interview notes or analytics, correct the AI's guesses. Every correction carries into features and stories.
What's next
- Turn personas into functionality → Generating features
- Not sure your description is rich enough? → Writing effective prompts