👤
FrontendMarkdown

User Persona

by Owl-Listener

User Persona is a Frontend skill for Claude Code, published by Owl-Listener in designer-skills.

2.1K stars335 forkson Owl-Listener/designer-skillsAdded 2026/08/18+2% in starsRepository updated 2026/08/08
agenticagentic-aiaiai-toolsclaude-codedesign-systemdesign-systemsprompt-engineeringskillsux-design
Install in seconds
Install User Persona
Copy User Persona into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/user-persona ~/.claude/skills/user-persona

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/Owl-Listener/designer-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
design-research/skills/user-persona/SKILL.md in Owl-Listener/designer-skills
Installs to
~/.claude/skills/user-persona
Collection
One of 25 skills cataloged from this repository
Category
Frontend — 732 skills

What User Persona does

User Persona builds research-grounded personas with goals, frustrations, and behavioral patterns. Use it when product or UX decisions need a consistent user reference.

User Persona is cataloged under Frontend on DirSkills. User Persona comes from a repository tagged agentic, agentic-ai, ai, ai-tools and claude-code.

Documentation

README

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about User Persona

  • What else does Owl-Listener publish alongside User Persona?

    User Persona is one of 25 skills that DirSkills catalogs from Owl-Listener/designer-skills, the repository it ships in. Its siblings there include Accessibility Audit, Affinity Diagram and Card Sort Analysis. Each one is a separate skill with its own page in this directory, installs the same way User Persona does, and is maintained by Owl-Listener in that same repository. The rest of the collection is listed on the Owl-Listener/designer-skills page.

  • How does User Persona compare to other Frontend skills?

    User Persona ranks #248 by stars among the 732 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of User Persona against them. Open each page to compare what they document and how they install.

More from Owl-Listener/designer-skills

User Persona is one of 25 skills cataloged on DirSkills from Owl-Listener/designer-skills.

See all 25 skills →
♿
2026/08/18

Accessibility Audit

Accessibility Audit examines an existing interface against WCAG criteria, identifies barriers, and provides severity-rated findings with remediation steps. Use it when you have a design or build to assess now, not for planning future assistive-technology testing sessions.
Quality
2.1K335
🗂️
2026/08/18

Affinity Diagram

Affinity Diagram clusters qualitative data points into themes and insight statements. Use it when synthesising across multiple sessions or sources to create a structured hierarchy with supporting evidence.
Data
2.1K335
🗂️
2026/08/18

Card Sort Analysis

Card Sort Analysis analyzes open or closed card sort results into a proposed grouping and label set. Use it after running a sort study to inform navigation and content organization.
Frontend
2.1K335
🧩
2026/08/18

Component Spec

Component Spec specifies one component's props, states, variants, accessibility, and usage rules. Use when defining a library component.
Frontend
2.1K335
💬
2026/08/18

Design Critique

Design Critique facilitates structured team critique sessions, guiding framing, feedback rules, and actionable outcomes. Use it when running a session with people in the room to keep feedback constructive and aligned.
Frontend
2.1K335
🔍
2026/08/18

Design Debt Audit

Design Debt Audit inventories and prioritizes accumulated design inconsistencies across a product so teams can plan remediation. Use it before redesigns or when UI drift, accessibility gaps, and structural debt have built up.
Frontend
2.1K335