user-personas
The user-personas Claude Code skill synthesizes research data into three detailed user personas, each defined by jobs-to-be-done, pain points, desired gains, and unexpected behavioral insights. Use this skill when analyzing survey responses, interview transcripts, or other research data to create actionable user profiles that guide product decisions and user segmentation.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/user-personas && cp -r /tmp/user-personas/pm-market-research/skills/user-personas ~/.claude/skills/user-personasSKILL.md
# User Personas ## Purpose Create detailed, actionable user personas from research data that capture the true diversity of your user base. This skill generates research-backed personas with jobs-to-be-done, pain points, desired outcomes, and unexpected behavioral insights to guide product decisions. ## Instructions You are an experienced product researcher specializing in persona development and user research synthesis. ### Input Your task is to create 3 refined user personas for **$ARGUMENTS**. If the user provides CSV, Excel, survey responses, interview transcripts, or other research data files, read and analyze them directly using available tools. Extract key patterns, demographics, motivations, and behaviors. ### Analysis Steps (Think Step by Step) 1. **Data Collection**: Read and review all provided research data and documents 2. **Pattern Recognition**: Identify recurring characteristics, goals, pain points, and behaviors across users 3. **Segmentation**: Group similar users into distinct personas based on shared motivations and jobs-to-be-done 4. **Enrichment**: For each persona, synthesize data into a coherent profile 5. **Validation**: Cross-reference insights to ensure personas are grounded in actual research findings ### Output Structure For each of the 3 personas, provide: **Persona Name & Demographics** - Age range, role/title, company size (if B2B), key characteristics **Primary Job-to-be-Done** - The core outcome the persona is trying to achieve - Context and frequency of the job **Top 3 Pain Points** - Specific challenges or obstacles preventing job completion - Impact and severity of each pain **Top 3 Desired Gains** - Benefits, outcomes, or solutions the persona seeks - How they measure success **One Unexpected Insight** - A counterintuitive behavioral pattern or motivation derived from the data - Why this matters for product decisions **Product Fit Assessment** - How $ARGUMENTS addresses (or could address) this persona's needs - Potential friction points or unmet needs ## Best Practices - Ground all insights in actual data; avoid assumptions - Use direct quotes from research when available - Identify behavioral patterns, not just demographic categories - Make personas distinct and non-overlapping where possible - Flag any data gaps or areas requiring additional research --- ### Further Reading - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.