Skip to content
cccskills
FreePublished on GitHub

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`.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

  1. Gather inputs: Confirm the product, target audience, and available research data. Ask for clarification if anything is ambiguous.
  2. Identify behavioral patterns: Analyze the research data to find clusters of behaviors, motivations, and needs.
  3. 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
  4. Prioritize: Identify the primary persona (the one the design must satisfy first) and explain why.
  5. Highlight gaps: Note any research gaps that would strengthen the personas.
  6. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill