30 Claude Prompts That Build Buyer Personas

You are a consumer-brand strategist who builds vivid, behavior-driven customer personas. <context> I need a single B2C customer persona for my product, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and category: [WHAT IT IS] - Price point: [RANGE] - Rough target audience: [WHO] - The need or desire it satisfies: [FUNCTIONAL AND EMOTIONAL] - How people typically discover it: [CHANNELS] - A real customer detail I know: [ANY NOTE] </inputs> <task> Build the persona card with: header (name, age, location, photo placeholder, a one-line tagline), lifestyle and demographics, the functional and emotional jobs the product does for them, their goals and aspirations, frustrations with current options, purchase triggers and hesitations, the brands and channels they trust, and a natural first-person quote. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Capture both the practical need and the emotional driver; avoid stereotypes and clichés. - Accessible contrast and semantic markup; the quote should sound like a real person on social media. </constraints> <format> Return the persona card as an artifact, then name the one emotional driver you would lead with in ad creative for this persona. </format>

You are a customer-insights analyst who synthesizes personas from voice-of-customer data. <context> I will paste real reviews, support tickets, or social comments. Turn the dominant pattern into one persona, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The raw feedback (paste below): [REVIEWS / TICKETS / COMMENTS] - What I want to learn: [E.G. WHY THEY CHURN, WHAT THEY LOVE] </inputs> <task> Read the feedback, identify the most common type of customer, and build their persona card: header, the recurring goals and delights they express, the recurring complaints and pains, the exact phrases they use (verbatim language bank), what made them buy, what makes them stay or leave, and a representative first-person quote stitched from their real language. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Ground every trait in the supplied feedback; do not invent traits that have no support in the text. - Include a short note flagging anything you inferred versus saw directly; accessible markup. </constraints> <format> Return the persona card as an artifact, then list the three most frequent verbatim phrases so I can reuse them in marketing copy. </format>

You are a brand planner who builds psychographic personas around values and identity. <context> I need a persona defined less by demographics and more by values, identity, and lifestyle, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or brand: [WHAT IT IS] - The identity it lets people express: [E.G. ECO-CONSCIOUS, MINIMALIST] - Values that matter to this audience: [LIST] - Where they spend attention: [PLATFORMS, COMMUNITIES] - A brand they already love: [EXAMPLE] </inputs> <task> Build the psychographic persona card with: header and a one-line identity statement, core values and beliefs, what they want to signal to others, the lifestyle and habits behind the purchase, the tensions or guilt they feel about choices, the communities and creators they follow, the brands they consider "their people", and a first-person quote expressing their worldview. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Lead with psychographics over demographics; show the identity the product helps them perform. - Accessible, expressive but legible layout; the quote should feel authentic, not preachy. </constraints> <format> Return the persona card as an artifact, then suggest one brand-values message that would resonate without sounding performative. </format>

You are a growth-focused product marketer for consumer mobile apps. <context> I need a persona for the typical user of my consumer mobile app, focused on how and when they use it, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - App and core job: [WHAT IT DOES] - Platform and price model: [IOS/ANDROID, FREE/FREEMIUM/PAID] - Primary use occasion: [E.G. COMMUTE, BEFORE BED] - The habit it builds or replaces: [NOTE] - Why people might churn: [NOTE] </inputs> <task> Build the persona card with: header, the trigger and moment they open the app, their goal in a single session, the friction in onboarding or daily use, what makes them form a habit versus uninstall, the notifications and nudges they tolerate, how they found the app, their willingness to pay or upgrade, and a first-person quote about how the app fits their day. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Center the persona on usage occasions and retention behavior, not just demographics. - Accessible markup; the quote should sound like an app-store review in real life. </constraints> <format> Return the persona card as an artifact, then suggest the one onboarding moment most likely to determine whether this user sticks. </format>

You are an e-commerce conversion strategist who studies buyers who purchase for someone else. <context> Many of my buyers are not the end user, they are buying a gift. I need that gift-buyer persona as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - Who the gift is usually for: [RECIPIENT] - The gifting occasion: [BIRTHDAY, HOLIDAYS, ETC] - The buyer's relationship to recipient: [E.G. PARENT, PARTNER] - Their worry when gifting: [E.G. WILL THEY LIKE IT] </inputs> <task> Build the persona card with: header, what they are really trying to achieve emotionally (be a thoughtful giver), how they shop differently than a self-buyer, the reassurances they need (returns, sizing, will it land), the time pressure of the occasion, the channels and signals that make them trust a product as a safe gift, the price comfort zone, and a first-person quote about the gifting stress. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Distinguish clearly how a gift-buyer's motivations and anxieties differ from the end user's. - Accessible, scannable layout; the quote should sound like someone gift-shopping under a deadline. </constraints> <format> Return the persona card as an artifact, then suggest the one trust signal (e.g. easy returns, gift receipt) that would most lift gift conversions. </format>

You are a senior UX researcher who builds design-ready user personas. <context> I need a UX persona to anchor product design decisions for a feature or product, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - The user's role or context: [E.G. FREELANCE DESIGNER] - Their primary goal with it: [JOB TO ACCOMPLISH] - Their technical comfort: [NOVICE / POWER USER] - Devices and environment: [WHERE THEY USE IT] - Known frustrations: [NOTES] </inputs> <task> Build the UX persona card with: header (name, role, photo placeholder, one-line bio), goals and motivations, key tasks and the contexts in which they happen, frustrations and pain points in the current flow, their tech proficiency and accessibility needs, the tools they already use, behaviors and mental models, and a first-person quote summarizing what they need from the product. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Make it actionable for designers: tie pains to specific tasks, not vague feelings; note any accessibility considerations. - Accessible markup and contrast; the quote should be need-focused, not promotional. </constraints> <format> Return the persona card as an artifact, then list three design implications (what to prioritize or simplify) that follow from this persona. </format>

You are a product strategist trained in the Jobs-to-Be-Done framework. <context> I want a persona built around the job the customer is hiring my product to do, not their demographics, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The struggle or moment that triggers a search: [SITUATION] - What they currently use instead: [WORKAROUND OR COMPETITOR] - The progress they want to make: [DESIRED OUTCOME] - What holds them back from switching: [ANXIETIES, HABITS] </inputs> <task> Build a JTBD persona card with: a job statement in the form "When [situation], I want to [motivation], so I can [expected outcome]", the functional, emotional, and social dimensions of the job, the triggering struggle, the push and pull forces (what pushes them from the old way, what pulls them to the new, and the anxieties and habits resisting change), the hiring criteria they judge solutions on, and a first-person quote about the moment they decided to look for something better. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Frame everything around the job and the four forces of progress, not demographics. - Accessible, structured layout; the quote should describe a concrete struggling moment. </constraints> <format> Return the JTBD persona card as an artifact, then suggest the one message that best speaks to the moment of struggle. </format>

You are a UX researcher who turns raw research notes into a defensible persona. <context> I will paste notes from user interviews or open-ended survey responses. Synthesize them into one persona, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or research goal: [WHAT WE WANTED TO LEARN] - Number of participants: [N] - The raw notes (paste below): [INTERVIEW / SURVEY NOTES] </inputs> <task> Analyze the notes, cluster recurring patterns, and build a persona card: header, goals and motivations supported by the data, pains and frustrations with quotes, behaviors and workarounds observed, the decision criteria they voiced, contradictions or tensions across participants, a confidence note on how strongly the data supports each trait, and a first-person quote drawn from real responses. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Every claim must trace to the notes; clearly separate observed data from inference. - Flag where the sample is thin or contradictory; accessible markup. </constraints> <format> Return the persona card as an artifact, then list the two open questions a follow-up study should answer to firm up this persona. </format>

You are an inclusive-design specialist who builds personas for users with diverse abilities. <context> I need a persona that centers accessibility needs so my team designs inclusively, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - The user context: [E.G. SCREEN-READER USER, LOW VISION, MOTOR] - Their primary goal: [JOB TO DO] - Assistive tech they use: [E.G. VOICEOVER, SWITCH CONTROL] - Environment and constraints: [NOTES] </inputs> <task> Build the persona card with: header, the user's goals and the tasks they need to complete, the assistive technologies and settings they rely on, the specific barriers they hit in typical interfaces, what good and bad experiences feel like to them, the WCAG-aligned needs this implies (contrast, focus order, labels, timing), and a respectful first-person quote about being designed for, not around. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be specific and respectful; avoid inspiration tropes; tie needs to concrete design requirements. - The card itself must be a model of accessibility: high contrast, semantic markup, clear focus. </constraints> <format> Return the persona card as an artifact, then list four concrete accessibility requirements this persona makes non-negotiable. </format>

You are a product designer who maps how users evolve from first-run to mastery. <context> I need two contrasting personas for the same product, a brand-new user and a power user, side by side, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The new user's first goal: [INITIAL JOB] - The power user's advanced goals: [DEEP JOBS] - The biggest first-run obstacle: [NOTE] - The features power users live in: [LIST] </inputs> <task> Build a two-column card comparing: each persona's goal, mental model and expectations, the friction they feel, what "value" means to each, the features that matter to each, the support they need, the risk of losing each (early churn vs. plateau), and a first-person quote per persona. Make the contrast obvious so the team sees the gap. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - The two personas must feel genuinely different in needs and risks, not just labeled new and advanced. - Accessible, balanced two-column layout that stacks cleanly on mobile. </constraints> <format> Return the paired persona card as an artifact, then name the single feature or moment that should help the new user become the power user. </format>

You are a marketing strategist who defines who NOT to target to sharpen positioning. <context> I need a negative persona, a profile of the person we should deliberately not pursue, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and value: [WHAT IT DOES] - Who keeps signing up but never succeeds: [PATTERN] - Why they are a bad fit: [REASONS] - The cost of serving them: [SUPPORT LOAD, CHURN, REFUNDS] - How they tend to find us: [CHANNEL] </inputs> <task> Build the negative persona card with: header (with a clear "do not target" badge), the traits and expectations that make them a poor fit, why our product will disappoint them, the support burden and churn they create, the marketing messages that accidentally attract them, the disqualifying signals to watch for, and a first-person quote showing their mismatched expectation. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be specific and fair: this is about fit, not insulting anyone; tie each trait to a concrete mismatch. - Accessible markup; visually distinguish this as a negative persona (e.g. muted/red accent). </constraints> <format> Return the negative persona card as an artifact, then suggest one copy or targeting change that would attract fewer of these poor-fit prospects. </format>

You are a retention strategist who profiles the customer most likely to leave. <context> I need a persona for my highest churn-risk customer so I can intervene earlier, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and plan: [WHAT IT IS] - When churn usually happens: [E.G. MONTH 2, AFTER TRIAL] - Behaviors that precede churn: [LOW LOGINS, NO INVITE, ETC] - The unmet need behind churn: [GUESS] - The save offers I can make: [DISCOUNT, ONBOARDING, ETC] </inputs> <task> Build the churn-risk persona card with: header, the early-warning behaviors that flag this risk, the moment value failed to land, the unmet expectation driving the exit, what they would have needed to stay, the intervention timing and message that could save them, the save offers most likely to work, and a first-person quote capturing their disappointment at the cancel moment. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Tie every signal to an observable behavior so it can power a real churn-prediction rule. - Accessible markup; the quote should sound like a cancellation-survey response. </constraints> <format> Return the churn-risk persona card as an artifact, then propose one early-warning trigger and the intervention to fire when it hits. </format>

You are a conversion copywriter who specializes in objection handling. <context> I need a persona for the prospect who is interested but deeply skeptical, so I can pre-empt their doubts, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and claim: [WHAT IT DOES, THE BIG PROMISE] - Why they doubt it: [PAST DISAPPOINTMENTS, RISK] - The objections they raise: [LIST] - Proof I can offer: [CASE STUDIES, GUARANTEE, DATA] - What they have tried before: [COMPETITORS, DIY] </inputs> <task> Build the skeptic persona card with: header, the root of their distrust, the specific objections in their own words, what evidence would actually move them, the risk-reducers (guarantee, trial, proof) they need, the tone that earns their trust versus the tone that loses it, and a first-person quote dripping with reasonable doubt. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Take their doubts seriously; pair each objection with the proof that answers it. - Accessible markup; the quote should sound like an arms-crossed buyer, not a hater. </constraints> <format> Return the skeptic persona card as an artifact, then write one headline plus subhead that disarms this persona's single biggest objection. </format>

You are a pricing and positioning strategist who profiles the most price-sensitive buyer. <context> I need a persona for the buyer who leads with price and budget, so I can decide whether and how to serve them, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and pricing model: [WHAT IT IS, HOW IT IS PRICED] - Their budget reality: [TIGHT, FIXED, APPROVAL-HEAVY] - What they compare on: [FEATURES, PRICE-PER-SEAT, FREE TIER] - The cheaper alternatives they weigh: [DIY, FREE TOOLS] - What would justify a higher spend: [ROI ANGLE] </inputs> <task> Build the price-first persona card with: header, their budget context and approval process, how they evaluate value versus cost, the comparisons and trade-offs they make, the objections about price, the ROI framing or proof that justifies the spend, when they are a worthwhile customer versus a margin trap, and a first-person quote about the budget conversation. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be honest about when this buyer is and is not worth pursuing; tie value framing to concrete ROI. - Accessible markup; the quote should sound like a real budget-defending buyer. </constraints> <format> Return the price-first persona card as an artifact, then suggest one ROI-framing line that shifts the conversation from cost to value. </format>

You are a competitive positioning strategist who profiles buyers switching from a rival. <context> I need a persona for the customer leaving a specific competitor for us, so I can ease the switch, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The competitor they are leaving: [NAME OR TYPE] - Why they are unhappy there: [PUSH REASONS] - What pulls them toward us: [OUR ADVANTAGE] - Their switching fears: [DATA MIGRATION, LEARNING CURVE] </inputs> <task> Build the switcher persona card with: header, the breaking-point that pushed them to look, what they liked and will miss about the old tool, the must-haves they refuse to lose in a switch, the migration anxieties (data, retraining, downtime), the proof and onboarding help they need to commit, the language they use to describe the old tool's failures, and a first-person quote about being fed up. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Respect what the old tool did well; switching is about removing fear, not bashing the rival. - Accessible markup; the quote should sound like a frustrated-but-cautious switcher. </constraints> <format> Return the switcher persona card as an artifact, then suggest one migration-reassurance offer that would remove this persona's biggest switching fear. </format>

You are a market segmentation strategist who builds comparable persona sets. <context> I need three distinct personas covering my main customer segments, presented together for comparison, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - My three rough segments: [E.G. SOLO, SMALL TEAM, ENTERPRISE] - What differs most between them: [NEEDS, BUDGET, SCALE] - The shared core value: [WHAT ALL THREE WANT] </inputs> <task> Build a three-up persona set where each card shares the same structure: header, primary goal, top pain, decision driver, budget and buying behavior, preferred channel, and a one-line quote. Use a consistent template so the three are directly comparable, and add a short summary noting where they overlap and where they diverge. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - All three personas use identical fields for true comparability; each must be clearly distinct. - Accessible three-column layout that stacks on mobile; no filler. </constraints> <format> Return the three-persona set as an artifact, then recommend which segment to prioritize first and why. </format>

You are a UX strategist who maps a persona spectrum from core to edge cases. <context> I need a persona spectrum showing my primary user plus the edge users at the extremes, so design decisions account for the range, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - The primary (most common) user: [WHO] - An extreme power-needs edge user: [WHO] - An extreme low-context or constrained edge user: [WHO] - The dimension that varies most: [E.G. EXPERTISE, FREQUENCY] </inputs> <task> Build a spectrum card placing three personas along the key dimension: the primary user in the center, an edge user at each extreme. For each, give goal, context, capability, and the design accommodation they need. Add a note on which edge case, if designed for, would also improve the experience for the majority. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Visually represent the spectrum (e.g. a horizontal scale) and keep the three personas comparable. - Accessible markup; tie each persona to a concrete design accommodation. </constraints> <format> Return the persona spectrum as an artifact, then name the edge case worth designing for first because it also lifts the mainstream user. </format>

You are a B2B sales strategist who maps the full buying committee. <context> My deals involve several people. I need a mini-persona for each buying-committee role on one card, so my team can sell to the whole group, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and deal size: [WHAT IT IS, RANGE] - The roles typically involved: [E.G. CHAMPION, ECONOMIC BUYER, USER, IT, FINANCE] - Who usually drives the deal: [ROLE] - The most common blocker role: [ROLE] </inputs> <task> Build a committee map where each role gets a compact mini-persona: what they care about, what they fear, the question they will ask, the proof that wins them, and their influence level (high/medium/low). Add a short line on the order to win them in and where deals usually stall. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Each role's motivation must be distinct; show how to tailor the pitch per role. - Accessible grid layout; clearly mark influence level for each role. </constraints> <format> Return the buying-committee map as an artifact, then recommend the sequence to win the committee and the role to enlist as champion. </format>

You are a product marketer who builds decision-ready persona comparison matrices. <context> I have several personas and need them compared in one matrix so the team can see differences at a glance, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The personas to compare: [2-4 PERSONA NAMES OR DESCRIPTIONS] - The dimensions that matter to me: [E.G. GOAL, PAIN, BUDGET, CHANNEL, OBJECTION] </inputs> <task> Build a comparison matrix with personas as columns and the chosen dimensions as rows. Fill each cell with a tight, specific value. Add a final row recommending the priority and the single sharpest message for each persona, and a short takeaway under the table. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - The matrix must be scannable: short, concrete cell values, not paragraphs. - Accessible table markup with header scopes; responsive on mobile. </constraints> <format> Return the persona comparison matrix as an artifact, then call out the one dimension where the personas diverge most, because that is where targeting matters. </format>

You are a head of product marketing who packages a persona for an executive audience. <context> I need a polished, single-page persona summary for leadership and sales enablement, not a research deck, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The persona this is about: [NAME OR DESCRIPTION] - The key facts I want front and center: [GOAL, PAIN, OBJECTION, CHANNEL] - The business stake: [WHY THIS PERSONA MATTERS COMMERCIALLY] </inputs> <task> Build an executive persona one-pager: a clean header, a one-line "why this persona matters" business framing, the core profile (goals, pains, objections, channels) as tight cards, a "how we win them" summary, the proof and messaging that work, and a single memorable quote. Make it presentation-ready and confident. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Lead with the commercial stakes; keep it skimmable in under a minute. - Polished, professional design; accessible contrast and semantic markup. </constraints> <format> Return the persona one-pager as an artifact, then suggest the one slide-worthy stat or quote to open a sales kickoff with. </format>

You are a design-thinking facilitator who builds empathy maps. <context> I need an empathy map for one persona, structured as the classic says/thinks/does/feels quadrants, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The persona: [NAME OR DESCRIPTION] - The scenario or moment to map: [E.G. EVALUATING TOOLS] - Anything I already know they say or feel: [NOTES] </inputs> <task> Build an empathy map with four quadrants (SAYS, THINKS, DOES, FEELS) around the persona, plus a pains strip and a gains strip below. Fill each quadrant with specific, scenario-grounded entries that reveal the gap between what they say and what they really think or feel. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Make the contrast between SAYS and THINKS revealing, not redundant; ground entries in the scenario. - Accessible four-quadrant layout that stacks on mobile; clear labels. </constraints> <format> Return the empathy map as an artifact, then name the single insight from the gap between what they say and what they feel. </format>

You are a CX strategist who maps customer journeys to a specific persona. <context> I need a stage-by-stage journey map for one persona, showing what they do, think, and feel at each step, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The persona: [NAME OR DESCRIPTION] - The journey scope: [E.G. AWARENESS TO PURCHASE, OR TRIAL TO RENEWAL] - Known touchpoints: [WEBSITE, EMAIL, SUPPORT, ETC] </inputs> <task> Build a journey map across stages (e.g. Awareness, Consideration, Decision, Onboarding, Retention) with, per stage: the persona's goal, their actions, their thoughts and emotions, the touchpoints, the friction or drop-off risk, and the opportunity to help. Add an emotional curve indication and flag the highest-friction stage. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Tie every stage back to this specific persona's motivations, not a generic funnel. - Accessible, horizontally scannable layout that stacks on mobile. </constraints> <format> Return the journey map as an artifact, then name the one moment of friction to fix first for the biggest conversion lift. </format>

You are a positioning strategist who turns a persona into a messaging brief. <context> I have a persona and need it translated into ready-to-use messaging, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The persona (paste or summarize): [GOALS, PAINS, OBJECTIONS, CHANNELS] - Our differentiator: [WHY US] - The action we want: [SIGN UP, BOOK DEMO, ETC] </inputs> <task> Build a messaging brief card with: the persona's core pain in their words, the value proposition aimed at that pain, three benefit-led headlines, three objection-handling lines (objection then rebuttal), the proof points that land for them, the tone and vocabulary to use and avoid, and a sample CTA. Everything tailored to this one persona. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Every line must map to a trait in the persona; no generic copy that could fit anyone. - Accessible, copy-ready layout; the language should match the persona's vocabulary. </constraints> <format> Return the messaging brief as an artifact, then pick the single strongest headline and explain why it fits this persona best. </format>

You are a narrative researcher who brings personas to life through storytelling. <context> I need a day-in-the-life narrative for a persona, showing where my product fits into their real day, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The persona: [NAME, ROLE, CONTEXT] - Their typical day shape: [WORK PATTERN, RESPONSIBILITIES] - The moment our product helps: [WHEN AND WHY] - Their biggest daily frustration: [PAIN] </inputs> <task> Build a narrative card walking through the persona's day in a short timeline (morning, midday, afternoon, evening), showing their tasks, the moments of friction, the trigger where they reach for a solution, and where our product naturally fits, in vivid but believable prose. Close with a short reflection on the unmet need the story reveals. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Keep it grounded and realistic; show the product fitting in, not magically solving everything. - Accessible timeline layout; story should be specific, not a generic montage. </constraints> <format> Return the day-in-the-life card as an artifact, then name the single moment in the story where our product creates the most obvious value. </format>

You are a research lead who pressure-tests personas before teams act on them. <context> I have a draft persona built partly on assumptions. I need a validation checklist to confirm or kill it with real research, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The draft persona (paste or summarize): [KEY TRAITS] - What we based it on: [DATA, GUESSES, SALES NOTES] - Resources to validate: [INTERVIEWS, SURVEY, ANALYTICS] </inputs> <task> Build a validation checklist card that, for each major persona claim (goal, pain, objection, channel, buying behavior), states the assumption, rates current evidence (strong/weak/none), gives the cheapest way to test it, and the question to ask. Add a go/no-go gate: which claims must be validated before the team builds on this persona. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be honest about which claims are guesses; prioritize the riskiest assumptions to test first. - Accessible checklist layout with clear evidence ratings. </constraints> <format> Return the validation checklist as an artifact, then name the single riskiest assumption to test before anyone relies on this persona. </format>