User Persona

Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use `empathy-map`; for motivation framing use `jobs-to-be-done`.

3,414 stars 447 forksResearch & Science Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill user-persona
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-research/skills/user-persona ~/.claude/skills/user-persona

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# User Persona

Create comprehensive user personas grounded in research data for product and UX design.

## Context

You are a senior UX researcher helping a design team create user personas for $ARGUMENTS. If the user provides files (research data, interview transcripts, survey results, analytics), read them first. If they mention a product URL, use web search to understand the product.

## Domain Context

- Personas (Alan Cooper, About Face): Archetypical users based on behavioral patterns, not demographics alone.
- Each persona should feel like a real person the team can empathize with and design for.
- Personas should be grounded in actual research data, not assumptions.
- Include behavioral variables, goals (life goals, experience goals, end goals), and frustrations.

## Instructions

The user will describe their product and available research data. Work through these steps:

1. **Gather inputs**: Confirm the product, target audience, and available research data. Ask for clarification if anything is ambiguous.
2. **Identify behavioral patterns**: Analyze the research data to find clusters of behaviors, motivations, and needs.
3. **Define 2-4 personas** — for each persona, include:
   - Name, photo description, and a one-line quote that captures their mindset
   - Demographics: age range, occupation, tech comfort, relevant context
   - Goals: what they want to achieve (functional, emotional, social)
   - Frustrations: current pain points and unmet needs
Read the full skill on GitHub

Details

Skill name
user-persona
Path
design-research/skills/user-persona/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the User Persona skill do?

Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use `empathy-map`; for motivation framing use `jobs-to-be-done`.

How do I install the User Persona skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is User Persona popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Sw Genre Anatomy

2.1k

jtydhr88/screenwriting-skills

Genre anatomy from John Truby's The Anatomy of Genres (类型解剖 / 类型节拍 / 混合类型 / 超越类型) — genres as beat systems with a life philosophy underneath; three rules (hit every beat of your genre, mix three or four genres, transcend the primary genre), the ladder and families of twelve genres (Horror 恐怖, Action 动作, Myth 神话, Memoir and Coming-of-Age 回忆录与成长, Science Fiction 科幻, Crime 犯罪, Comedy 喜剧, Western 西部, Gangster 黑帮, Fantasy 奇幻, Detective and Thriller 侦探与惊悚, Love 爱情), each with its hero/opponent/world/plot-shape template, beat list, hard rules with failure conditions, subgenres and transcendent paths,

Research & Science220

Research Repository

3.4k

Owl-Listener/designer-skills

Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.

Research & Science447

Crw Research

1.3k

fastcrw/crw

Find ALL the arXiv papers that answer a research question, using fastCRW's Firecrawl-compatible Research API. Use when the ask is to survey a literature, enumerate papers on a topic, find what a paper compares against or builds on, list the best models on a benchmark, or recover a paper from a vague description — "papers that do X", "what does X benchmark against", "best open model on Y", "find the paper that ...". Reaches 61.0% recall on the ArXivQA benchmark vs Firecrawl's Research Index 53.3%.

Research & ScienceIn 1 list102

Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.