Skip to main content
skill CX Codex

user-persona — Claude Code skill: what it does, how to install

This skill builds 2-4 research-grounded personas from interview transcripts, surveys, or analytics. It helps teams align design decisions with observed user behavior.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill user-persona -a claude-code
Open on GitHub

What user-persona does

The assistant acts as a senior UX researcher to define two to four archetypes following Alan Cooper's methodology. Each persona receives a quote, behavioral traits, goals, frustrations, a day-in-the-life narrative, and concrete design implications. When the generated report is extensive, the skill saves it as a Markdown file directly in the workspace.

Real interview transcripts or survey summaries serve as primary inputs. Without research files, the agent searches the web for product details, which risks falling back on assumptions. After detailing the personas, the skill prioritizes the primary profile that the product must satisfy first and highlights research gaps.

If you only need an emotional snapshot of a single session, use empathy-map instead; for framing customer motivation, switch to jobs-to-be-done.

What it helps with

  • synthesize interview transcripts into structured user profiles
  • determine the primary persona to prioritize product features
  • map user frustrations and goals to concrete design decisions
  • pinpoint research gaps before drafting interface requirements

Example prompts for the agent

  • Create user personas for our service based on interviews.txt
  • Analyze the survey results in survey_results.csv and define 2-4 personas
  • Build personas for our product and highlight any gaps in the research data

How to install user-persona

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill user-persona -a claude-code

2Manually: put the files in place

~/.claude/skills/user-persona/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/user-persona/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about user-persona

How do I install user-persona in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill user-persona -a claude-code in your terminal.

What does user-persona do?

It examines research files to define two to four archetypes with their goals, pain points, daily scenarios, and design implications. The skill also highlights the primary persona and flags missing research data.

How does user-persona differ from empathy-map and jobs-to-be-done?

The user-persona skill models behavioral archetypes for continuous reference. If you need a snapshot of user emotions during a single session, use empathy-map, and choose jobs-to-be-done to frame underlying motivations.

Source text

SKILL.md · MIT
---
name: user-persona
description: 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`.
---

# 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
   - Behaviors: how they currently approach the problem
   - Scenario: a brief day-in-the-life narrative
   - Design implications: what this means for product decisions
4. **Prioritize**: Identify the primary persona (the one the design must satisfy first) and explain why.
5. **Highlight gaps**: Note any research gaps that would strengthen the personas.
6. Think step by step. Present personas in a clear, structured format. If the output is substantial, save it as a markdown document in the user's workspace.

## Further Reading

- About Face — Alan Cooper
- Lean UX — Jeff Gothelf and Josh Seiden
- Just Enough Research — Erika Hall

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

From the same set111

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor