Builds a realistic user persona from what you know about your users, with goals, frustrations and needs to design for.
WHEN TO USE IT
When you are designing something and need a clear picture of who it is for.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: user-persona
description: Create a user persona from research notes or what the user knows about their audience. Use when the user asks for a persona, a target user profile or who to design for.
---
Create a user persona.
1. If the product, the audience or any research notes are missing, ask once, in one message, then continue.
2. Write the persona:
- Name and a one-line description (the name is invented and marked as such)
- Context: role, setting and how they use similar products
- Goals: three things they want to achieve
- Frustrations: three things that get in their way
- Needs from the product: what would make it work for them
- A typical day or scenario, in four or five sentences
3. Add "Based on": which points come from research and which are assumptions to test.
Rules:
- Do not invent statistics or quotes; label assumptions as [assumption].
- Avoid stereotypes about age, gender, region or ability.
- Keep it to one page so a team actually uses it.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/user-persona
mv SKILL.md ~/.claude/skills/user-persona/
# then, inside Claude Code, either ask naturally:
# make a user persona for my fitness app
# or run it by name:
# /user-persona
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills