agentleFS
lenar-amirovlenar-amirov/product-pipeline-public/.claude/skills/user-persona-builder/SKILL.md

user-persona-builder

Skill13 starsChanged 5 months agoMITView on GitHub

Creates detailed user personas from research data combining demographics, psychographics, behavioral patterns, goals, and pain points. Use when user needs to build personas, segment users, or says "user persona", "create persona", "user segments", "who is our user", "target audience profile", "персона пользователя", "создай персону".

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    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
  1. Distinctive:

    Always ground personas in real data:

    line 18
  2. Distinctive:

    Create one-page summary cards for quick reference

    line 139
  3. Distinctive:

    Create empathy maps linking personas to emotional journeys

    line 142
  4. Distinctive:

    Update based on product usage analytics

    line 153
  5. Distinctive:

    When real user interviews aren't available yet, build personas from secondary data as a starting point.

    line 159
  6. Distinctive:

    After real customer research (interviews/survey) arrives, update personas:

    line 214
  7. Distinctive:

    Add new personas discovered in interviews

    line 218
  8. Distinctive:

    Generic Demographics: Avoid surface-level descriptions without behavioral insights

    line 222
  9. Distinctive:

    Assumption-Based: Never create personas without substantial user research

    line 223
  10. Distinctive:

    Static Thinking: Update personas as your product and market evolve

    line 224
  11. Distinctive:

    Feature Bias: Don't let current product features limit persona development

    line 226

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are an expert in user research and persona development with deep knowledge of behavioral psychology, market segmentation, and product strategy. You excel at synthesizing quantitative data and qualitative insights to create actionable user personas that drive product decisions.

Core Persona Development Framework

Primary Persona Elements

  • Demographics: Age, location, income, education, occupation
  • Psychographics: Values, attitudes, lifestyle, personality traits
  • Behavioral patterns: Usage frequency, feature adoption, decision-making process
  • Goals & Motivations: Primary objectives, success metrics, aspirations
  • Pain Points & Frustrations: Current challenges, friction points, unmet needs
  • Context & Environment: Where/when they use the product, surrounding circumstances

Data Sources Integration

Always ground personas in real data:

  • User interviews and surveys
  • Analytics and usage data
  • Support tickets and feedback
  • Market research and competitive analysis
  • A/B test results and behavioral observations

Persona Template Structure

# [Persona Name] - "The [Archetype Title]"

## Quick Profile
- **Age**: X years old
- **Location**: [City, Country]
- **Occupation**: [Job Title]
- **Tech Comfort**: [Scale 1-10]
- **Quote**: "[Memorable quote that captures their essence]"

## Background & Context
[2-3 sentences about their life situation, work environment, and relevant background]

## Goals & Motivations
### Primary Goals
1. [Specific goal with measurable outcome]
2. [Secondary goal]
3. [Aspirational goal]

### Success Metrics
- [How they measure success]
- [Key performance indicators they care about]

## Pain Points & Challenges
### Current Frustrations
1. **[Pain Point Category]**: [Specific description and impact]
2. **[Pain Point Category]**: [Specific description and impact]

### Workarounds
- [Current solutions they use]
- [Limitations of existing approaches]

## Behavioral Patterns
### Product Usage
- **Frequency**: [Daily/Weekly/Monthly usage pattern]
- **Peak Times**: [When they're most active]
- **Preferred Channels**: [Mobile/Desktop/Email preferences]
- **Feature Adoption**: [Which features they use/ignore]

### Decision Making Process
1. [Recognition of need]
2. [Research approach]
3. [Evaluation criteria]
4. [Purchase/adoption triggers]

## Scenarios & Use Cases
### Primary Use Case
**Scenario**: [Detailed walkthrough of main usage scenario]
**Context**: [Surrounding circumstances]
**Expected Outcome**: [What success looks like]

### Edge Cases
- [Less common but important scenarios]

## Influence & Environment
- **Key Influencers**: [Who affects their decisions]
- **Information Sources**: [Where they get information]
- **Social Context**: [Team/family/community considerations]

Research-Driven Best Practices

Quantitative Foundation

  • Base demographic splits on actual user data (80%+ of users should map to personas)
  • Include usage statistics: session length, feature adoption rates, conversion funnels
  • Reference specific survey data points and sample sizes
  • Connect behavioral segments to business metrics

Qualitative Depth

  • Include direct quotes from user interviews
  • Describe emotional states and psychological drivers
  • Map user journey emotions from awareness to advocacy
  • Identify trigger events that change behavior patterns

Persona Validation Checklist

## Validation Criteria
- [ ] Based on data from at least 15-20 user interviews
- [ ] Represents 15%+ of user base
- [ ] Contains specific, actionable insights
- [ ] Includes measurable goals and success metrics
- [ ] Addresses both functional and emotional needs
- [ ] Identifies clear differentiation from other personas
- [ ] Connects to business objectives
- [ ] Regularly updated with new research findings

Advanced Persona Techniques

Jobs-to-be-Done Integration

For each persona, define:

  • Functional Job: What practical task they're trying to accomplish
  • Emotional Job: How they want to feel during the process
  • Social Job: How they want to be perceived by others

Persona Prioritization Matrix

High Impact + High Volume = Primary Personas (2-3 max)
High Impact + Low Volume = Secondary Personas
Low Impact + High Volume = Optimization Targets
Low Impact + Low Volume = Deprioritize

Dynamic Persona Elements

Include evolving characteristics:

  • Maturity Stages: How needs change as users become more experienced
  • Seasonal Variations: Usage pattern changes throughout the year
  • Life Stage Evolution: How major life events affect product needs

Implementation & Activation

Persona Distribution

  • Create one-page summary cards for quick reference
  • Develop persona-based user story templates
  • Build persona decision trees for feature prioritization
  • Create empathy maps linking personas to emotional journeys

Cross-functional Usage

Product: Feature prioritization, roadmap planning Design: User experience optimization, interaction design Marketing: Messaging, channel strategy, campaign targeting Sales: Qualification criteria, objection handling Support: FAQ prioritization, self-service content

Persona Maintenance

  • Review quarterly with new research data
  • Update based on product usage analytics
  • Validate assumptions through ongoing user testing
  • Retire outdated personas that no longer represent significant user segments

Early-Stage Personas (synthetic research, before real data)

When real user interviews aren't available yet, build personas from secondary data as a starting point. Mark all outputs as SYNTHETIC evidence.

Secondary Data Sources

  • App store reviews: Pain points in competitors' products
  • Support tickets: Common complaints and feature requests (if available)
  • Market reports: Segment demographics, behavior patterns
  • Competitor UX: Who are competitors designing for?
  • Community forums: Reddit, ProductHunt, industry Slack groups
  • Analytics data: Behavioral clusters from existing product usage

Persona Confidence Scorecard

Rate confidence for each persona trait:

| Trait | Value | Confidence | Source |
|-------|-------|-----------|--------|
| Age range | 25-35 | Medium | Market report + app reviews |
| Primary goal | Save time on X | High | 15+ reviews mention this |
| Pain point | Can't do Y on mobile | Low | Only 2 anecdotal mentions |
| Behavior | Uses tool daily | Medium | Competitor analytics blog |
  • High: 3+ independent sources confirm
  • Medium: 1-2 sources, logically consistent
  • Low: Single source or inference — needs validation

Synthetic Interview Template

For each persona, simulate a problem-focused interview (5-7 questions):

## Persona: [Name], [Role]
**Background**: [2-3 sentences from secondary data]

### Interview Simulation
Q1: "Walk me through the last time you [relevant scenario]."
> "[Simulated response based on secondary data patterns]"

Q2: "What was most frustrating about that experience?"
> "[Response grounded in identified pain points]"

Q3: "What did you try before giving up / finding a workaround?"
> "[Response based on competitor usage and support ticket patterns]"

[Continue 5-7 questions]

### Synthesis
- **Confirmed patterns**: [What multiple sources agree on]
- **Hypothesized patterns**: [Inferred from limited data — mark as LOW confidence]
- **Blind spots**: [What we can't know without real interviews]

Upgrading to REAL

After real customer research (interviews/survey) arrives, update personas:

  • Replace SYNTHETIC traits with interview-backed REAL evidence
  • Adjust confidence scores based on actual user data
  • Retire personas that don't match real user segments
  • Add new personas discovered in interviews

Common Pitfalls to Avoid

  • Generic Demographics: Avoid surface-level descriptions without behavioral insights
  • Assumption-Based: Never create personas without substantial user research
  • Static Thinking: Update personas as your product and market evolve
  • Too Many Personas: Limit to 3-5 primary personas to maintain focus
  • Feature Bias: Don't let current product features limit persona development
  • Internal Politics: Base persona priority on data, not internal team preferences

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.