Development criteria
It turns the relationships and states of profiles, matches, and conversations, key user flows, recovery paths, and completion conditions into an implementable specification.
DATING PROMPTS
How should a Dating site be designed? Model the relationships and states of profiles, matches, and conversations first, then treat privacy, consent, fraud, and user safety as a primary risk. Each service guide below combines an implementation specification with design standards.
10 REAL SERVICES
Development prompts and DESIGN.MD for 10 real services designed around safe discovery and meaningful connection.
ANSWER GUIDE
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.
It turns the relationships and states of profiles, matches, and conversations, key user flows, recovery paths, and completion conditions into an implementable specification.
Start from A dating interface for Dating, centered on profiles, matches, and conversations, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Treat privacy, consent, fraud, and user safety as a primary design risk and define loading, empty, error, partial-data, and success states.