Discover / Empathize

Framework-driven prompt patterns for discover / empathize workflows.

Affinity Mapping

Clusters observations into themes.

# CONTEXT
Phase: Discover / Empathize
Method: Affinity Mapping
Inputs provided: [OBSERVATIONS], [METHODS]

# ASK
What insights, outputs, or clarity should this affinity mapping generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Themes with evidence matrix and strength ratings

Ensure the final output is practical and usable in real product workflows.

C.A.R.E enforces evidence and quality.

Card Sorting (Open/Closed)

Reveals mental models for grouping labels.

# ROLE
Act as a senior UX specialist for Card Sorting (Open/Closed) within the Discover / Empathize phase.

# TASK
Using the following inputs: [ITEM SET], [AUDIENCE], [OPEN/CLOSED],
deliver a high-quality card sorting (open/closed) outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Recruiting; Instructions; Card/category list; Similarity analysis; IA recommendation

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F requires a concrete, stepwise plan.

Competitive / Market Analysis

Understand alternatives, table stakes, and differentiators.

# CONTEXT
Phase: Discover / Empathize
Method: Competitive / Market Analysis
Inputs provided: [CATEGORY], [SEGMENT], [NUMBER OF COMPETITORS]

# ASK
What insights, outputs, or clarity should this competitive / market analysis generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Table-stakes vs differentiators table; Design principles

Ensure the final output is practical and usable in real product workflows.

C.A.R.E balances breadth with critical analysis.

Context Mapping / Ecosystem Map

Visualizes people, systems, and influences around the user.

# CONTEXT
Phase: Discover / Empathize
Method: Context Mapping / Ecosystem Map
Inputs provided: [SEGMENT], [SITUATION], [STAKEHOLDERS]

# ASK
What insights, outputs, or clarity should this context mapping / ecosystem map generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Entities; Relationships; Data flows; Policies; Pain points; Dependencies/risks/opportunities

Ensure the final output is practical and usable in real product workflows.

C.A.R.E keeps focus on comprehension.

Diary Study / User Diary

Self-reported longitudinal behavior.

# ROLE
Act as a senior UX specialist for Diary Study / User Diary within the Discover / Empathize phase.

# TASK
Using the following inputs: [BEHAVIOR], [SEGMENT], [DURATION],
deliver a high-quality diary study / user diary outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Brief; Prompts; Reminder cadence; Incentive plan; Wrap-up survey/interview

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F standardizes a repeatable study.

Empathy Map

Captures what users Say/Think/Do/Feel.

# CONTEXT
Phase: Discover / Empathize
Method: Empathy Map
Inputs provided: [SEGMENT], [CONTEXT], [NOTES/TRANSCRIPTS]

# ASK
What insights, outputs, or clarity should this empathy map generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Filled empathy map; Tensions; Opportunities

Ensure the final output is practical and usable in real product workflows.

C.A.R.E prioritizes synthesis and evidence.

Focus Groups

Group discussion to surface shared language and tensions.

# CONTEXT
Phase: Discover / Empathize
Method: Focus Groups
Inputs provided: [TOPIC], [SEGMENT], [SIZE], [SETTING]

# ASK
What insights, outputs, or clarity should this focus groups generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
90-minute guide; Solo → share → converge; Captured quotes/artifacts; Tensions list

Ensure the final output is practical and usable in real product workflows.

C.A.R.E emphasizes learning quality with a concrete example.

Funnel / Metrics Review

Quant view of acquisition→activation→retention.

# CONTEXT
Phase: Discover / Empathize
Method: Funnel / Metrics Review
Inputs provided: [DATES], [EVENTS], [SEGMENTS]

# ASK
What insights, outputs, or clarity should this funnel / metrics review generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Funnel report; Hypotheses; Experiment shortlist

Ensure the final output is practical and usable in real product workflows.

C.A.R.E connects data to insight and action.

Observation / Shadowing

Observe real behavior in context.

# CONTEXT
Phase: Discover / Empathize
Method: Observation / Shadowing
Inputs provided: [ENVIRONMENT], [TASK], [PERMISSIONS]

# ASK
What insights, outputs, or clarity should this observation / shadowing generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Observation plan; Field-note template; Coding scheme; Critical incidents log

Ensure the final output is practical and usable in real product workflows.

C.A.R.E balances rigor with practical constraints.

Stakeholder Interviews

Aligns business goals, constraints, success metrics.

# CONTEXT
Phase: Discover / Empathize
Method: Stakeholder Interviews
Inputs provided: [PROJECT], [ROLES], [DECISIONS]

# ASK
What insights, outputs, or clarity should this stakeholder interviews generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Interview guide + signals checklist + red-flags

Ensure the final output is practical and usable in real product workflows.

C.A.R.E blends discovery with explicit result and concrete example.

Surveys (Quantitative)

Measures attitudes/behaviors at scale.

# ROLE
Act as a senior UX specialist for Surveys (Quantitative) within the Discover / Empathize phase.

# TASK
Using the following inputs: [TOPIC], [AUDIENCE], [DECISION],
deliver a high-quality surveys (quantitative) outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Screeners; Core blocks; Scales & logic; Bias cautions; Pilot plan

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F yields a concrete, deployable instrument.

User Interviews

Structured conversations to understand behaviors, goals, pain points.

# ROLE
Act as a senior UX specialist for User Interviews within the Discover / Empathize phase.

# TASK
Using the following inputs: [TOPIC], [USER SEGMENT], [LEARNING GOAL], [DURATION],
deliver a high-quality user interviews outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Opening & current behaviors; Goals & motivations; Challenges & workarounds; Ideal experience & expectations; Probing follow-ups & transitions; Consent & wrap-up

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F creates a reusable, structured guide.

Define

Framework-driven prompt patterns for define workflows.

Assumptions Mapping / CSD Matrix

Surfaces Certainties, Suppositions, Doubts.

# CONTEXT
Phase: Define
Method: Assumptions Mapping / CSD Matrix
Inputs provided: [INITIATIVE], [STATEMENTS]

# ASK
What insights, outputs, or clarity should this assumptions mapping / csd matrix generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
C/S/D board; Risk scores; Test-backlog with owners/timebox

Ensure the final output is practical and usable in real product workflows.

C.A.R.E pairs assumptions with validation.

Competitive Audit (Flows)

Benchmarks flows & patterns across competitors.

# CONTEXT
Phase: Define
Method: Competitive Audit (Flows)
Inputs provided: [FLOW NAME], [NAMES], [NUMBER OF COMPETITORS]

# ASK
What insights, outputs, or clarity should this competitive audit (flows) generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Step table with pattern/risk/opportunity; Accessibility notes

Ensure the final output is practical and usable in real product workflows.

C.A.R.E prioritizes analysis over collection.

OKRs / Success Metrics

Defines outcomes and measures.

# CONTEXT
Phase: Define
Method: OKRs / Success Metrics
Inputs provided: [OBJECTIVE], [TIMEFRAME]

# ASK
What insights, outputs, or clarity should this okrs / success metrics generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Objective; 2-3 KRs; Indicators; Guardrails; Assumptions

Ensure the final output is practical and usable in real product workflows.

C.A.R.E connects metrics to decisions.

Personas

Evidence-based archetypes for design.

# TASK
Execute the Personas activity using these inputs:
[COUNT], [NOTES], [CONTEXT]

# ACTION
Break down the concrete steps, analysis, or structure required to complete this properly within the Define phase.

# GOAL
The goal is to produce:
Snapshot; Behaviors; JTBD; Channels; Accessibility

Make the outcome measurable, structured, and aligned to UX decision-making standards.

T.A.G makes the evaluator's action and goal explicit.

Problem Statement (POV)

Captures the design challenge crisply.

# CONTEXT
Phase: Define
Method: Problem Statement (POV)
Inputs provided: [TOPIC], [SEGMENT]

# ASK
What insights, outputs, or clarity should this problem statement (pov) generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
POV statement; 3-5 HMWs with evidence links

Ensure the final output is practical and usable in real product workflows.

C.A.R.E guards clarity and evidence.

Task Analysis / HTA Diagram

Breaks a goal into tasks, subtasks, decisions.

# ROLE
Act as a senior UX specialist for Task Analysis / HTA Diagram within the Define phase.

# TASK
Using the following inputs: [GOAL], [USER],
deliver a high-quality task analysis / hta diagram outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
HTA: goal→tasks→subtasks→actions; Preconditions; Errors/edge cases; Opportunities

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F produces a scannable artifact.

Value Proposition

Articulates value from user perspective.

# BEFORE
Describe the current state, limitations, or problems related to Value Proposition.
Use these inputs: [SEGMENT], [JOB]

# AFTER
Define the ideal improved state or outcome expected from this activity within the Define phase.

# BRIDGE
Explain the structured steps, analysis, or transformation required to move from BEFORE to AFTER.

Final deliverable must follow this structure:
Before; After; Bridge; Value prop sentence; 3 bullets; Objections & counters

Highlight assumptions, risks, and practical implementation considerations.

B.A.B highlights transformation.

Ideate & Map

Framework-driven prompt patterns for ideate & map workflows.

2×2 Matrix

Visual selection by two criteria.

# CONTEXT
Phase: Ideate & Map
Method: 2×2 Matrix
Inputs provided: [OPTIONS], [X-AXIS], [Y-AXIS]

# ASK
What insights, outputs, or clarity should this 2×2 matrix generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
2×2 placement; Justifications; Top 3 picks; Risks/unknowns

Ensure the final output is practical and usable in real product workflows.

C.A.R.E prioritizes decision quality.

Benefit Matrix / Impact-Effort

Prioritizes ideas by value vs complexity.

# CONTEXT
Phase: Ideate & Map
Method: Benefit Matrix / Impact-Effort
Inputs provided: [LIST], [IMPACT], [EFFORT], [CONSTRAINTS]

# ASK
What insights, outputs, or clarity should this benefit matrix / impact-effort generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Scored list; Quadrants; Top-10; Next validation steps

Ensure the final output is practical and usable in real product workflows.

C.A.R.E makes trade-offs explicit.

Brainstorm Session Plan

Guides divergent idea generation.

# ROLE
Act as a senior UX specialist for Brainstorm Session Plan within the Ideate & Map phase.

# TASK
Using the following inputs: [PROBLEM], [TEAM SIZE],
deliver a high-quality brainstorm session plan outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Run-sheet with rules; 10 seeds; Timeboxes; Parking lot; Next steps

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F gives a ready-to-run plan.

Concept Map / Relationship Map

Shows domain concepts and relationships.

# CONTEXT
Phase: Ideate & Map
Method: Concept Map / Relationship Map
Inputs provided: [DOMAIN]

# ASK
What insights, outputs, or clarity should this concept map / relationship map generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Concept nodes; Relationship edges; Definitions; Open questions

Ensure the final output is practical and usable in real product workflows.

C.A.R.E aligns vocabulary and structure.

Crazy 8s

Forces 8 ideas in 8 minutes.

# TASK
Execute the Crazy 8s activity using these inputs:
[ROLES], [SKILLS]

# ACTION
Break down the concrete steps, analysis, or structure required to complete this properly within the Ideate & Map phase.

# GOAL
The goal is to produce:
Setup; Framings; Timing; Selection rubric

Make the outcome measurable, structured, and aligned to UX decision-making standards.

T.A.G clarifies evaluator actions toward a goal.

Dot Voting

Democratic prioritization.

# ROLE
Act as a senior UX specialist for Dot Voting within the Ideate & Map phase.

# TASK
Using the following inputs: [IDEAS],
deliver a high-quality dot voting outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Voting criteria; Dots per person; Process; Tie-break rule

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F yields a fair, repeatable process.

Journey Map / Experience Map

Stages, goals, emotions, opportunities.

# CONTEXT
Phase: Ideate & Map
Method: Journey Map / Experience Map
Inputs provided: [PERSONA], [GOAL], [SOURCES]

# ASK
What insights, outputs, or clarity should this journey map / experience map generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Stages; Touchpoints; Emotions; Pain points; Opportunities; KPIs

Ensure the final output is practical and usable in real product workflows.

C.A.R.E favors depth and evidence.

Kano Model

Classifies features (Must/Performance/Delighter).

# CONTEXT
Phase: Ideate & Map
Method: Kano Model
Inputs provided: [FEATURE LIST], [SEGMENT]

# ASK
What insights, outputs, or clarity should this kano model generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Kano survey; Scoring; Feature classes; Release recs

Ensure the final output is practical and usable in real product workflows.

C.A.R.E requires methodological rigor.

Mind Map

Expands associative space around a topic.

# CONTEXT
Phase: Ideate & Map
Method: Mind Map
Inputs provided: [TOPIC], [SEGMENT]

# ASK
What insights, outputs, or clarity should this mind map generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Mind map branches; Top 5 opportunities with rationale

Ensure the final output is practical and usable in real product workflows.

C.A.R.E emphasizes exploration and structure.

MoSCoW Prioritization

Must/Should/Could/Won't classifications.

# TASK
Execute the MoSCoW Prioritization activity using these inputs:
[FEATURES], [RELEASE/TIMEBOX]

# ACTION
Break down the concrete steps, analysis, or structure required to complete this properly within the Ideate & Map phase.

# GOAL
The goal is to produce:
MoSCoW tables with acceptance criteria and risks

Make the outcome measurable, structured, and aligned to UX decision-making standards.

T.A.G structures the decision.

RICE Scoring

Prioritizes by Reach, Impact, Confidence, Effort.

# ROLE
Act as a senior UX specialist for RICE Scoring within the Ideate & Map phase.

# TASK
Using the following inputs: [ITEMS],
deliver a high-quality rice scoring outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
RICE table with definitions

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F outputs a clear, sharable table.

SCAMPER

Idea transformation using 7 lenses.

# ROLE
Act as a senior UX specialist for SCAMPER within the Ideate & Map phase.

# TASK
Using the following inputs: [OBJECT/PROCESS],
deliver a high-quality scamper outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
SCAMPER table with 3 ideas per lens + notes

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F ensures coverage across lenses.

Service Blueprint

Maps frontstage/backstage to deliver the journey.

# ROLE
Act as a senior UX specialist for Service Blueprint within the Ideate & Map phase.

# TASK
Using the following inputs: [SERVICE/SCENARIO],
deliver a high-quality service blueprint outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Blueprint lanes: Customer; Frontstage; Backstage; Support; Evidence/KPIs

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F yields a canonical blueprint.

Site Map / IA

Organizes information into navigable structure.

# ROLE
Act as a senior UX specialist for Site Map / IA within the Ideate & Map phase.

# TASK
Using the following inputs: [PRODUCT/DOMAIN],
deliver a high-quality site map / ia outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Sections; URLs/labels; Cross-links; Search facets; Accessibility/SEO notes

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F produces a concrete IA draft.

Prototype

Framework-driven prompt patterns for prototype workflows.

Accessibility & Compliance

Ensures inclusive, legal experiences.

# CONTEXT
Phase: Prototype
Method: Accessibility & Compliance
Inputs provided: [LEVEL], [PLATFORM], [FEATURE]

# ASK
What insights, outputs, or clarity should this accessibility & compliance generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Checklist; Assistive tech notes; Test plan; Common pitfalls

Ensure the final output is practical and usable in real product workflows.

C.A.R.E makes quality criteria explicit.

Copywriting

Clear, helpful interface copy.

# ROLE
Act as a senior UX specialist for Copywriting within the Prototype phase.

# TASK
Using the following inputs: [FLOW], [TONE], [LEVEL], [LOCALE],
deliver a high-quality copywriting outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Screen/Element/Copy table; Variants; Microcopy incl. ARIA

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F outputs concrete, shippable copy.

Design System Starter

Reusable components, tokens, guidelines.

# CONTEXT
Phase: Prototype
Method: Design System Starter
Inputs provided: [PRODUCT]

# ASK
What insights, outputs, or clarity should this design system starter generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Tokens; Core components; Usage rules; Accessibility targets; Adoption & versioning

Ensure the final output is practical and usable in real product workflows.

C.A.R.E balances consistency with guardrails.

Micro-interactions

UX details that guide and delight.

# ROLE
Act as a senior UX specialist for Micro-interactions within the Prototype phase.

# TASK
Using the following inputs: [TRIGGER], [CONTEXT],
deliver a high-quality micro-interactions outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Trigger; Rules; Feedback; States; Timing; Accessibility

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F ensures coverage of states.

Mockups & High-Fidelity

Visual design directions.

# BEFORE
Describe the current state, limitations, or problems related to Mockups & High-Fidelity.
Use these inputs: [PRODUCT], [BRAND ATTRIBUTES]

# AFTER
Define the ideal improved state or outcome expected from this activity within the Prototype phase.

# BRIDGE
Explain the structured steps, analysis, or transformation required to move from BEFORE to AFTER.

Final deliverable must follow this structure:
Before; After; Bridge; Spec table with tokens and do/don't

Highlight assumptions, risks, and practical implementation considerations.

B.A.B connects vision to UI choices.

Paper Prototypes

Rapid, low-fidelity screens to test flows.

# ROLE
Act as a senior UX specialist for Paper Prototypes within the Prototype phase.

# TASK
Using the following inputs: [FLOW],
deliver a high-quality paper prototypes outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Screen list; Test script; Capture grid

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F produces runnable materials.

Wireframes

Structural layout without visual polish.

# ROLE
Act as a senior UX specialist for Wireframes within the Prototype phase.

# TASK
Using the following inputs: [SCREEN/FEATURE],
deliver a high-quality wireframes outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Components & hierarchy; Actions; States; Errors/loading/responsiveness

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F prescribes content and states.

Test / Validate

Framework-driven prompt patterns for test / validate workflows.

A/B Testing

Compare variants to estimate lift.

# CONTEXT
Phase: Test / Validate
Method: A/B Testing
Inputs provided: [METRIC], [BASELINE], [TRAFFIC]

# ASK
What insights, outputs, or clarity should this a/b testing generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Hypothesis; Sample size; Guardrails; Stop rules; Launch checklist; Decision framework

Ensure the final output is practical and usable in real product workflows.

C.A.R.E requires statistical rigor.

Analytics Review

Turns product analytics into UX decisions.

# CONTEXT
Phase: Test / Validate
Method: Analytics Review
Inputs provided: [EVENTS], [DATES], [SEGMENTS]

# ASK
What insights, outputs, or clarity should this analytics review generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Friction/dead-ends/success paths; 3 design changes + effect size

Ensure the final output is practical and usable in real product workflows.

C.A.R.E emphasizes inference → action.

Desirability Testing

Measures emotional response to concepts.

# TASK
Execute the Desirability Testing activity using these inputs:
[CONCEPT], [SEGMENT]

# ACTION
Break down the concrete steps, analysis, or structure required to complete this properly within the Test / Validate phase.

# GOAL
The goal is to produce:
Adjective set; Script; Analysis plan

Make the outcome measurable, structured, and aligned to UX decision-making standards.

T.A.G links evaluation to a decision goal.

Eye-Tracking / Attention Mapping

Understand visual attention patterns.

# ROLE
Act as a senior UX specialist for Eye-Tracking / Attention Mapping within the Test / Validate phase.

# TASK
Using the following inputs: [SCREEN/FLOW],
deliver a high-quality eye-tracking / attention mapping outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Equipment/assumptions; Tasks/AOIs; Metrics; Cautions

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F requires specific setup & metrics.

Heuristic Evaluation

Expert review against heuristics.

# CONTEXT
Phase: Test / Validate
Method: Heuristic Evaluation
Inputs provided: [PRODUCT/SCREEN], [HEURISTIC SET]

# ASK
What insights, outputs, or clarity should this heuristic evaluation generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Findings with severity/evidence/fix; Top issues summary

Ensure the final output is practical and usable in real product workflows.

C.A.R.E ties findings to criteria.

Pilot Test

Small-scale rehearsal to catch issues early.

# CONTEXT
Phase: Test / Validate
Method: Pilot Test
Inputs provided: [STUDY TYPE], [NUMBER OF PARTICIPANTS]

# ASK
What insights, outputs, or clarity should this pilot test generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Objectives; Success criteria; Observations; Go/No-Go; Fixes

Ensure the final output is practical and usable in real product workflows.

C.A.R.E focuses learning & gate criteria.

SUS / UMUX-Lite Survey

Standardized usability scores.

# ROLE
Act as a senior UX specialist for SUS / UMUX-Lite Survey within the Test / Validate phase.

# TASK
Using the following inputs: [PRODUCT/FEATURE],
deliver a high-quality sus / umux-lite survey outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Survey items; Scoring worksheet; Benchmarks; Interpretation

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F delivers a ready scoring kit.

Unmoderated / Remote Test

Scale testing asynchronously.

# CONTEXT
Phase: Test / Validate
Method: Unmoderated / Remote Test
Inputs provided: [URL], [PLATFORM], [MINUTES]

# ASK
What insights, outputs, or clarity should this unmoderated / remote test generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Tasks; Metrics; Attention checks; Exclusion rules; Thresholds; Sample size

Ensure the final output is practical and usable in real product workflows.

C.A.R.E enforces quality in remote tests.

Usability Testing (Moderated)

Observe task success and friction.

# ROLE
Act as a senior UX specialist for Usability Testing (Moderated) within the Test / Validate phase.

# TASK
Using the following inputs: [PROTOTYPE],
deliver a high-quality usability testing (moderated) outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Screener; Consent; 5 tasks + criteria; Probes; Severity scale; Debrief

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F returns a ready-to-run plan.

Artifacts & Operations

Framework-driven prompt patterns for artifacts & operations workflows.

Business Model Canvas

Captures how value is created & sustained.

# TASK
Execute the Business Model Canvas activity using these inputs:
[CONCEPT]

# ACTION
Break down the concrete steps, analysis, or structure required to complete this properly within the Artifacts & Operations phase.

# GOAL
The goal is to produce:
Complete BMC; Consistency check; Risks

Make the outcome measurable, structured, and aligned to UX decision-making standards.

T.A.G stays oriented to decision quality.

Copy Concept Testing

Compares messages for clarity & resonance.

# CONTEXT
Phase: Artifacts & Operations
Method: Copy Concept Testing
Inputs provided: [CONCEPTS], [SEGMENT]

# ASK
What insights, outputs, or clarity should this copy concept testing generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Remote test plan; Metrics; Counterbalancing; Report with scores/quotes/reco

Ensure the final output is practical and usable in real product workflows.

C.A.R.E combines qual + quant rigor.

RACI Matrix

Clarifies RACI responsibilities.

# ROLE
Act as a senior UX specialist for RACI Matrix within the Artifacts & Operations phase.

# TASK
Using the following inputs: [NAME], [TASK LIST], [ROLES],
deliver a high-quality raci matrix outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
RACI table; Conflict resolution; Mitigations

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F yields clear ownership.

Site/Skill/Landscape Maps

Inventory of pages, skills, or assets.

# ROLE
Act as a senior UX specialist for Site/Skill/Landscape Maps within the Artifacts & Operations phase.

# TASK
Using the following inputs: [SCOPE],
deliver a high-quality site/skill/landscape maps outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Entities; Groupings/gaps; Recommendations/owners

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F produces an actionable inventory.

Storyboard / Scenario Map

Visual narrative of user achieving a goal.

# BEFORE
Describe the current state, limitations, or problems related to Storyboard / Scenario Map.
Use these inputs: [USER], [GOAL]

# AFTER
Define the ideal improved state or outcome expected from this activity within the Artifacts & Operations phase.

# BRIDGE
Explain the structured steps, analysis, or transformation required to move from BEFORE to AFTER.

Final deliverable must follow this structure:
Before; After; Bridge; 6-8 panels

Highlight assumptions, risks, and practical implementation considerations.

B.A.B emphasizes narrative arc.

Style Guide / Design Principles

North-star rules for decisions.

# BEFORE
Describe the current state, limitations, or problems related to Style Guide / Design Principles.
Use these inputs: [SEGMENT]

# AFTER
Define the ideal improved state or outcome expected from this activity within the Artifacts & Operations phase.

# BRIDGE
Explain the structured steps, analysis, or transformation required to move from BEFORE to AFTER.

Final deliverable must follow this structure:
Before; After; Bridge; Principles with do/don't and rules

Highlight assumptions, risks, and practical implementation considerations.

B.A.B moves from critique to aspiration.

Usability Report

Communicates test findings and next steps.

# CONTEXT
Phase: Artifacts & Operations
Method: Usability Report
Inputs provided: [NUMBER OF USABILITY ISSUES], [LINK], [STUDY TYPE]

# ASK
What insights, outputs, or clarity should this usability report generate to move the project forward?

# RULES
- Follow UX best practices.
- Make outputs specific, not generic.
- Highlight risks and edge cases.
- State assumptions explicitly.

# EXAMPLES
Format the response according to:
Findings with severity/evidence/fix; Prioritized actions with owners

Ensure the final output is practical and usable in real product workflows.

C.A.R.E emphasizes evidence and prioritization.

User Story Map

Organizes backlog by user activities and slices.

# ROLE
Act as a senior UX specialist for User Story Map within the Artifacts & Operations phase.

# TASK
Using the following inputs: [PERSONA], [GOAL],
deliver a high-quality user story map outcome that drives clarity and decision-making.

# FORMAT
Structure your response exactly as:
Activities→steps→stories; Release slices; Risks/assumptions

Ensure outputs are actionable, structured, and decision-ready. State assumptions clearly if inputs are incomplete.

R.T.F outputs a ready planning view.

UX Roadmap

Sequenced plan across quarters with outcomes.

# BEFORE
Describe the current state, limitations, or problems related to UX Roadmap.
Use these inputs: [BUSINESS OBJECTIVES], [HORIZON]

# AFTER
Define the ideal improved state or outcome expected from this activity within the Artifacts & Operations phase.

# BRIDGE
Explain the structured steps, analysis, or transformation required to move from BEFORE to AFTER.

Final deliverable must follow this structure:
Before; After; Bridge; Roadmap table

Highlight assumptions, risks, and practical implementation considerations.

B.A.B communicates change over time.