Development criteria
It turns the relationships and states of events, seats, and tickets, key user flows, recovery paths, and completion conditions into an implementable specification.
EVENTS PROMPTS
Events and tickets website prompts
How should a Events and tickets site be designed? Model the relationships and states of events, seats, and tickets first, then treat inventory, timing, and refund terms as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- event discovery and admission
- Core entities
- events, seats, and tickets
- Design risk
- inventory, timing, and refund terms
10 REAL SERVICES
Events and tickets · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around event discovery and admission.
ANSWER GUIDE
Events and tickets 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 events interface for Events and tickets, centered on events, seats, and tickets, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat inventory, timing, and refund terms as a primary design risk and define loading, empty, error, partial-data, and success states.