Step 1 of 6
Define marketplace entities and rules
Two-sided products fail without clear roles and states - define them first.
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.
Expected after this step
A concrete spec of models, status flow, and marketplace rules.
Should not happen
- ✕Listings stored in local state and lost on refresh
- ✕Search that filters a hardcoded array
- ✕An order button that only shows a success toast
- ✕Buyers and sellers seeing the same generic dashboard
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !Listings stored in local state and lost on refresh
- !Search that filters a hardcoded array
- !An order button that only shows a success toast
- !Buyers and sellers seeing the same generic dashboard
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
The spec lacks an order status flow or ownership rules. Add the explicit status transitions and who can do what on each entity.