user-persona
Skill1 starsChanged 3 months agoMITView on GitHub
Interview one question at a time until a specific user persona is clear. Covers the moment, bio, goals, frustrations, and the rest, and recommends an answer on every question. Use when the user invokes /user-persona, asks to be grilled about their user, or wants a user persona before designing.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- fullstackinnoAI/skillstheir own version, first seen Nov 1, 2026
- SkillMedev/product-manager-stacktheir own version, first seen Oct 20, 2026
- miovrag/claude-skillstheir own version, first seen Jun 12, 2026
- launchapp-dev/animus-clitheir own version, first seen Mar 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- launchapp-dev/animus-cli★ 39same name
- fullstackinnoAI/skills★ 1same name
- miovrag/claude-skills★ 1same name
- SkillMedev/product-manager-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- cold-emailSkill
- desvibearSkill
- minimal-designSkill
- talk-decksSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If the project, files, or conversation already contain the fact, look it up and recommend that.
- Distinctive: line 18
If you are inferring, label it as a recommendation and say what it rests on.
- Distinctive: line 23
Ask in the user's language.
- Distinctive: line 33
Other stuff: Keep asking while something still fuzzy would change a design decision: where they are, how much time they have, who is with …
- Distinctive: line 37
Stop only when all of these are true:
- Distinctive: line 57
Leave a field as unknown if the user did not confirm it.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
User persona
Interview until one specific person is clear. Do not design the screen. Do not stop while a required field is still a segment, a guess, or a blank.
How to ask
One question per message. Wait for the answer.
On every question, recommend information:
- If the project, files, or conversation already contain the fact, look it up and recommend that. Name the source.
- If you are inferring, label it as a recommendation and say what it rests on.
- Offer a sharper version when the answer is a segment, a demographic, or a role bucket.
The user confirms or corrects it. An unconfirmed recommendation is not part of the persona.
Ask in the user's language.
Order
Skip a question only when the user already answered it. Confirm that answer in one line, then continue.
- Moment. One sentence. In Spanish it starts with "Está a punto de…". In English, "They are about to…". It names what they are about to do, what they fear, and what they must decide today.
- Bio. Who this person is, specific enough to pick them out of a room.
- Goals. What they want out of this moment.
- Frustrations. What blocks them, what they fear, and what they have already tried.
- Other stuff. Keep asking while something still fuzzy would change a design decision: where they are, how much time they have, who is with them, what device they are on, what they refuse to do, and what done looks like for them.
Done
Stop only when all of these are true:
- The moment sentence is one person and one decision. It would become false if you swapped in a different product.
- Bio, goals, and frustrations are confirmed by the user.
- Other stuff has no open question that would change what gets designed.
Then write the persona and stop. Do not propose screens, flows, or copy.
Persona
Moment
Bio
Goals
Frustrations
Other stuff
Leave a field as unknown if the user did not confirm it. Do not fill it with a recommendation they skipped.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.