What this prompt does
This prompt makes the AI a senior product designer and frontend engineer designing a marketplace seller dashboard, returning real buildable component code rather than wireframe notes. It defines a top KPI row for sales, orders, and conversion with trend deltas; an "orders awaiting action" module surfacing what the seller must do next; an inventory-health panel flagging low and out-of-stock SKUs; a recent-reviews feed with quick-reply; an upcoming-payouts card; and a performance score with its underlying metrics. The [primary_goal] placeholder focuses the layout, and [store_type] sets the marketplace context.
The structure works because the trap in seller dashboards is showing data instead of the next action. The prompt keeps the top of the screen about what the seller must do today rather than vanity charts, anchored by the awaiting-action module. It also asks for responsive layout, loading and empty states, and accessible color contrast so the dashboard holds up in real use. The [stack] variable produces component code plus a short layout map of where each module sits. Pairing the KPI row's trend deltas with concrete modules like inventory health and upcoming payouts means the numbers point somewhere actionable, so a seller who sees a dip in conversion or a low-stock flag knows the specific lever to pull rather than just staring at a chart.
When to use it
- Designing a seller or vendor dashboard for a marketplace
- Focusing the layout on a
[primary_goal]like fulfilling orders fast - Building for a
[store_type]such as a multi-vendor marketplace - You want the next action surfaced, not just vanity charts
- Adding inventory health flags for low and out-of-stock SKUs
- Showing payouts and a performance score with its metrics
Example output
You get component code for the dashboard plus a short layout map of where each module sits. The top KPI row shows sales, orders, and conversion with trend deltas; the orders-awaiting-action module surfaces the seller's next tasks; the inventory-health panel flags low and out-of-stock SKUs; the reviews feed allows quick-reply; and the payouts card sits alongside a performance score that exposes the metrics behind it. Loading and empty states and accessible contrast are included.
Pro tips
- Set
[primary_goal]to the outcome sellers care about most; it focuses what the top of the dashboard surfaces - Tailor
[store_type]so the modules and metrics fit your marketplace model - Wire the awaiting-action count to a real query early; padding it with fake numbers hides layout problems
- Keep
[stack]accurate so the component code and layout map fit your framework - Ask the model to keep vanity charts below the fold so the next action stays prominent
- Request that the performance score show the metrics behind it, so sellers understand how to improve it
