user-persona
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`.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill user-personaSKILL.md
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:
- Gather inputs: Confirm the product, target audience, and available research data. Ask for clarification if anything is ambiguous.
- Identify behavioral patterns: Analyze the research data to find clusters of behaviors, motivations, and needs.
- 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
- Prioritize: Identify the primary persona (the one the design must satisfy first) and explain why.
- Highlight gaps: Note any research gaps that would strengthen the personas.
- 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
Related skills
frontend-designanthropics932KGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.prototypemattpocock852KBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.hyperframes-animationheygen-com569KAll animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreographyhyperframes-creativeheygen-com539KNon-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.
