persona-gen — Claude Code skill for user personas
The persona-gen Claude Code skill builds user personas to clarify or choose a product’s audience. It produces three profiles and a priority matrix to guide which group to build for first.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill persona-gen -a claude-codeWhat persona-gen does
The skill creates three distinct user profiles and ranks them by urgency, willingness to pay, and reachability. Each profile covers a typical workday, goals, three specific frustrations, current workarounds, and buying behavior. A final matrix compares the personas and recommends which one to prioritize.
The skill needs details about the product and its market. It reads founder/facts.md, founder/product-brief.md, and founder/user-interviews.md, then saves its output to founder/persona-gen.md. Personas remain hypotheses until interviews validate them. When real interview notes are available, the skill builds on them and includes quotes.
What it helps with
- Map different audience segments to distinct user profiles
- Connect user frustrations with existing workarounds
- Rank customer groups by willingness to pay and reachability
- Choose which audience to build for first
Example prompts for the agent
- Create three personas for [product] in [target market].
- Use the interview notes and product brief to describe the likely users.
- Compare the audience segments and recommend which one to prioritize.
How to install persona-gen
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill persona-gen -a claude-code2Manually: put the files in place
~/.claude/skills/persona-gen/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/persona-gen/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill persona-gen -a codex2Manually: put the files in place
.agents/skills/persona-gen/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill persona-gen -a cursor2Manually: put the files in place
.cursor/skills/persona-gen/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/persona-gen2Manually: put the files in place
.github/skills/persona-gen/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill persona-gen -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/persona-genManually: put the files in place
.devin/skills/persona-gen/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill persona-gen -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about persona-gen
How do I install persona-gen in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill persona-gen -a claude-code. The skill file is at ~/.claude/skills/persona-gen/SKILL.md.
What does persona-gen do?
It creates three distinct user profiles covering their goals, frustrations, workarounds, and buying behavior. It then ranks them and recommends which audience to build for first.
What does persona-gen need to work?
It needs information about the product and the market it serves. The skill reads founder/facts.md, founder/product-brief.md, and founder/user-interviews.md; interview validation is needed to confirm the personas.
Source text
SKILL.md · MIT
---
name: persona-gen
description: Create 3 distinct user personas with a day in the life, quotable pain points, current workarounds, buying behavior, and a priority matrix showing who to build for first. Use when a founder needs to decide or describe who their customer is.
argument-hint: "[your product and target market]"
allowed-tools: Read Edit(founder/**)
---
You are a user research lead. You write personas that read like people a founder could go and find, not demographic summaries.
Input: $ARGUMENTS
## Before you start
Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it.
- Reads: `founder/facts.md`, `founder/product-brief.md`, `founder/user-interviews.md`
- Needs: the product and the market it serves
- Saves to: `founder/persona-gen.md`
These personas are hypotheses until interviews confirm them. Say so in one line at the top of the output. If the founder's input includes real interview notes, build from those and quote them.
## Instructions
Generate 3 distinct user personas. For each persona, provide:
### Persona template
**1. Identity**
- Name (realistic, not "Startup Steve")
- Age, location, job title
- Company size and stage (if B2B)
- Annual income range
**2. Day in the life**
3-4 sentences describing a typical workday. Include the tools they use, meetings they attend, and frustrations they hit.
**3. Goals and motivations**
- Primary goal (what they're trying to achieve this quarter)
- Secondary goal (what they care about but can't prioritize)
- Underlying motivation (why they care: career growth, financial pressure, personal mission)
**4. Pain points**
Exactly 3 frustrations related to the problem space. Each should be:
- Observable (you could see them doing this)
- Quotable (written as something they'd say in an interview)
- Actionable (the product could address it)
**5. Current workarounds**
What tools or processes do they use today to solve this problem?
- Tool name and what they use it for
- What's broken about this workaround
- How much time or money they lose on it per week (an estimate, with reasoning)
**6. Decision-making**
- How do they discover new tools? (X, Product Hunt, peer recommendations, Google search)
- What would make them try the product? (free trial, case study, a peer's recommendation)
- What would make them pay? (a specific trigger or pain threshold)
- Who else is involved in the buying decision? (for B2B)
**7. Product fit score**
- **Urgency** (1-5): How badly do they need this solved right now?
- **Willingness to pay** (1-5): How much budget and authority do they have?
- **Reachability** (1-5): How easy is it to find and market to them?
- **Overall priority:** Primary / Secondary / Tertiary
### After all 3 personas
**Persona priority matrix:** a small table ranking the 3 personas by urgency, willingness to pay, and reachability. Recommend which persona to build for first and why.
## Rules
- Each persona must be clearly different, not three versions of the same person.
- If the product is B2B, include at least one technical buyer and one economic buyer.
- Keep each persona under 400 words. Total output under 1500 words.
© emotixco · MIT · emotixco/claude-skills-founder