name	customer-persona
description	Turn a rough product idea or user-segment hunch into one structured Ember customer persona — goals, context-of-use, friction, a representative order, and three needs that shape acceptance criteria. Use when a PM or designer needs to ground a feature in who it's for before writing a PRD or design spec.

Customer Persona (Ember)

Turn a vague segment into one sharp, decision-ready persona for Ember, a food-delivery app (restaurants, menus, a cart, checkout, order history).

If the user already gave enough, skip ahead — don't interrogate.

Name & one-line identity — a real-feeling person, not a demographic.
Goals — 2–3, in their words.
Context of use — device, time, place, mood.
Friction today — where Ember's current flow fails them.
A representative order — real menu items and cart shape, using the actual Ember domain (restaurants, menu items, order lines).
Three needs that shape acceptance — testable, e.g. "re-order last meal in ≤2 taps".

Reference the real app — restaurants, menu items, the cart/checkout flow, order history. A persona that could belong to any app is a failed persona.

End by offering: "Feed this straight into /to-prd or the design spec." A persona composes into the next artifact — it isn't a dead end.

name	customer-persona
description	Turn a rough product idea or user-segment hunch into one structured Ember customer persona — goals, context-of-use, friction, a representative order, and three needs that shape acceptance criteria. Use when a PM or designer needs to ground a feature in who it's for before writing a PRD or design spec.

Turn a vague segment into one sharp, decision-ready persona for Ember, a food-delivery app (restaurants, menus, a cart, checkout, order history).

If the user already gave enough, skip ahead — don't interrogate.

Name & one-line identity — a real-feeling person, not a demographic.
Goals — 2–3, in their words.
Context of use — device, time, place, mood.
Friction today — where Ember's current flow fails them.
A representative order — real menu items and cart shape, using the actual Ember domain (restaurants, menu items, order lines).
Three needs that shape acceptance — testable, e.g. "re-order last meal in ≤2 taps".

Reference the real app — restaurants, menu items, the cart/checkout flow, order history. A persona that could belong to any app is a failed persona.

End by offering: "Feed this straight into /to-prd or the design spec." A persona composes into the next artifact — it isn't a dead end.

customer-persona