Development criteria
It turns the relationships and states of sellers, listings, and transactions, key user flows, recovery paths, and completion conditions into an implementable specification.
MARKETPLACE PROMPTS
Marketplaces website prompts
How should a Marketplaces site be designed? Model the relationships and states of sellers, listings, and transactions first, then treat trust and quality in a two-sided market as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- connecting suppliers and buyers
- Core entities
- sellers, listings, and transactions
- Design risk
- trust and quality in a two-sided market
10 REAL SERVICES
Marketplaces · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around connecting suppliers and buyers.
ANSWER GUIDE
Marketplaces How to choose a prompt
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
Design criteria
Start from A marketplace interface for Marketplaces, centered on sellers, listings, and transactions, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat trust and quality in a two-sided market as a primary design risk and define loading, empty, error, partial-data, and success states.