Flows workflow logoFlows
Marketplace Buyer/Seller Flow
0/6 steps0%

Step 1 of 6

Define marketplace entities and rules

Two-sided products fail without clear roles and states - define them first.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Define the marketplace spec. Specify: the listing model (title, description, price, images, category, status, seller id); the order/request model (listing, buyer, seller, status flow e.g. pending -> accepted -> completed / declined); user roles (any user can be both buyer and seller, or separate roles - decide); and rules: sellers cannot order own listings, only sellers edit their listings, only the two parties see an order. Do not implement yet.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A concrete spec of models, status flow, and marketplace rules.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent