Immediate result: Behaviour-based personas with goals, context, frustrations and quotes drawn from your research.
Problem it solvesPersonas are invented in workshops and describe stereotypes, not behaviour.
12 interviews with people who split bills with flatmates
'The Ledger Keeper' (5 of 12): pays first, tracks in Splitwise, chases everyone.
Quote: 'I'm always the one asking for ₹340 back.'
Implication: one-tap reminders that don't make the ledger keeper look petty.
Personas invented in workshops describe stereotypes, not behaviour. This skill clusters research participants by goals and behaviour rather than demographics, then writes each persona's goals, context, behaviours and frustrations with verbatim quotes and the number of participants it represents. It adds design implications and a list of what the research still doesn't tell you. Personas grounded this way survive contact with the product team because every claim points back to evidence. To use it, paste the skill into your assistant and send research notes, interview summaries or survey results; the reply is laid out as “Persona cards”, “Evidence count” and “Design implications”.
# Skill: Research-based persona
You are running the "Research-based persona" skill for me. I work as: UX researcher / designer. What I need from you: behaviour-based personas with goals, context, frustrations and quotes drawn from my research.
## When I send you research notes, interview summaries or survey results
1. Cluster participants by behaviour and goals, not demographics.
2. Write each persona's goals, context, behaviours and frustrations.
3. Include verbatim quotes and the number of participants it represents.
4. Note design implications.
## Reply in this format
- Persona cards
- Evidence count
- Design implications
- What we still don't know
## Rules
- No stock-photo demographics unless they matter to behaviour.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send research notes, interview summaries or survey results.Then sendResearch notes, interview summaries or survey results. For example: 12 interviews with people who split bills with flatmates
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/persona-builder ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/persona-builder ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/persona-builder/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Personas are invented in workshops and describe stereotypes, not behaviour. The skill fixes that: behaviour-based personas with goals, context, frustrations and quotes drawn from your research.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send research notes, interview summaries or survey results. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemFlows are designed screen by screen, and edge cases and dead ends get missed.
Booking a doctor's appointment in a clinic app
Happy path: choose specialty → doctor → slot → confirm → pay → confirmation
Branch: no slots this week → show next available + 'notify me'
States: slot taken during payment → hold for 5 minutes, then release
Immediate resultA complete user flow with happy path, decisions, error states and a Mermaid diagram.
ProblemColours and spacing are hard-coded everywhere, so the UI drifts and dark mode is painful.
Brand blue #2563EB, font Inter, 4px spacing grid, dark mode needed
--color-accent: #2563EB (light) / #60A5FA (dark)
Text on accent: #FFFFFF on #2563EB = 5.2:1 ✓
--space-1: 4px … --space-8: 32px
Immediate resultA token set for colour, type, spacing and radius in JSON and CSS variables, with light and dark values.
ProblemResearch starts with a method instead of a question, and the findings don't inform decisions.
Should we add a family plan to our streaming app?
Decision: build a family plan in Q1 or not.
RQ: How do households share accounts today, and what breaks?
Method: 10 household interviews + a survey of 400 subscribers on sharing.
Immediate resultA research plan: decision to inform, questions, method, participants, timeline and outputs.
All 12 design & ux skillsAll 200 skillsRead it in the articleProve it: AI for UX/UI Designers Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.