Overview
Create a persona that can be used to understand customers, product planning, and communication, organizing customer needs, pain points, behaviors, decision factors, and constraints. By default, deliver one Traditional Chinese persona; journey framing is an optional use enabled only when explicitly requested.
Input Contract
You can start from any of the following:
- Customer research, interviews, observations, or an existing persona.
- Target audience, preliminary profile, or usage scenario.
- A product or service and identifiable audience clues.
Also confirm the purpose of the persona, such as understanding user needs, product design, or communication planning. If the purpose is already clear, follow it; ask only about missing items that would change the direction of the analysis. Creating a persona does not require product names, journey stages, or touchpoint data as prerequisites.
By default, create one core persona; if the user requests multiple audience segments, handle them according to the request. When the behaviors or constraints of different audience segments are incompatible, explain the differences first, and avoid piecing them together into a nonexistent typical person.
Preserve mode: auto | persona-only | journey-framing：
auto: defaultpersona-only. Use that mode only when customer journey framing analysis is explicitly requested orjourney-framingis specified.persona-only: Deliver the persona, or review and revise an existing persona as requested.journey-framing: Based on the persona, add the user-requested journey framing content.
Mentioning emotions, touchpoints, stages, or 5W1H does not by itself justify switching modes. "Only persona" or "no journey for now" takes priority. When only a journey map is requested, hand it off to customer-journey-mapper; if that skill needs the customer profile filled in, this skill handles only the missing profile.
Data Sufficiency Gate
When the data is sufficient to identify the audience for this case and describe the needs, behaviors, and constraints relevant to the purpose, begin organizing. Information gaps should only limit the conclusions affected by them; complete the parts that can be determined first.
Distinguish three types of content:
- Research or known data: Preserve source names, interview numbers, or verifiable locations; avoid treating a single respondent's reaction directly as a general characteristic.
- Analytical inference: Explain the basis and the derivation relationship; when there is no evidence supporting generality, preserve the applicable conditions.
- Assumptions pending verification: When the user requests a draft or allows assumptions, propose necessary assumptions based on clues, with the number determined by the gaps, and explain how to confirm them.
"Just organize it for me directly" only means organizing existing data; it does not automatically authorize fabricating content. Demographic background, income, family, preferences, and quotations must be supported by data. Even when a draft is allowed, fictional personal details must not be written as research facts. Fields lacking data may be omitted or marked as pending confirmation, and should not be filled in with reasonable imagination.
When even the analysis target or purpose cannot be reasonably defined, confirm the key information first. Journey framing also follows Optional journey framing to determine the required data.
Workflow
1. Organize the basis and differences
Read existing data and confirm the purpose and scope of this task. Identify common characteristics based on observable behaviors, needs, decision-making methods, and constraints; preserve differences and counterexamples that would affect judgment. Research results or explicit corrections provided by the user take priority over older profiles.
2. Create the persona
Organize using the Output Contract below:
- Needs: What the customer wants to achieve and why it matters.
- Pain points: which obstacle currently makes the need hard to satisfy.
- Expectations: what outcome or experience the customer hopes for after improvement.
- Behavior and context: when, where, and how the customer handles the problem, and what approaches or alternatives they take.
- Decision factors: how the customer compares, accepts, or rejects options, and which conditions would change the choice.
- Constraints: how time, knowledge, budget, authority, device habits, etc. concretely affect action.
Maintain only one complete narrative for the same information, and reference it from other parts when needed. Role labels are used to identify the audience segment; age and life background are retained only when there is evidence and they affect the use case.
3. Deliver according to this scope
A general persona is delivered according to the structure below. When only a review or partial revision is requested, respond with the issues, evidence, or affected content, and reuse the rest of the valid data.
Only journey-framing reads optional journey prerequisites and adds the corresponding outputs. When a presentation-style summary is requested, retain the substantive content and rewrite it into bullet points suitable for slides, without adding journey analysis because of this. Actual slide files are handled according to the specified format.
Output Contract
Persona card
Use persona_block as the persona card body, and retain this name for later reference. Integrate the following information in the card, and do not repeat an identical summary at the end:
| Field | Content |
|---|---|
| Customer profile | Role label, represented audience segment, and related characteristics |
| Role background | Evidence-based background relevant to this case |
| Core needs | Main goals and their importance |
| Main pain points | Concrete obstacles in current approaches |
| Expectations | Desired outcomes or experiences |
| Usage context | When, where, and under what conditions the need is handled |
| Behavior and alternatives | Known approaches, habits, and alternative choices |
| Decision cues | Comparison criteria, adoption conditions, and reasons for rejection |
| Core constraints | Constraints with a real impact on action |
Data and inferences in the fields are accompanied by corresponding evidence, and assumptions are marked next to the relevant content. Unknown information is handled according to the Data Sufficiency Gate.
Necessary notes and items to confirm
Supplement with audience differences, data limitations, or key assumptions that affect interpretation, and list the information and methods that truly need confirmation. Do not restate fields that already have complete explanations. When delivering only a persona, end with the persona and necessary notes.
Quality Rules
- The persona enables readers to identify the customer and understand their needs and reasons for choosing.
- Needs, pain points, and expectations each have concrete content, and behavior and constraints are compatible.
- Characteristics have sources or clear inferential evidence, and assumptions do not masquerade as research facts.
- No stereotypes, fabricated quotes, or decorative background are used to fill out the card.
- The same information is written only once, and the original reusable fields and persona_block name are retained.
- Deliver the pre-journey purpose that matches the persona, partial review, or explicit specification.