What this prompt does
This prompt asks Claude or ChatGPT to design an event and wedding venue booking platform. You set [platform_name] and the [market_scope], then describe the [venue_types], the [event_types], the [lead_time], the [event_size], and the [framework]. The model designs venue discovery and search, the venue detail page, the inquiry and booking flow, a post-booking planning dashboard, catering and menu selection, day-of event management, and the framework implementation.
It works because a venue marketplace combines search, galleries, availability holds, and a planning dashboard — a multi-sided web app where the flows must stay coherent. By naming [venue_types] and [event_types], the model tailors filters and capacity breakdowns to your inventory. The [lead_time] variable shapes the planning timeline (a wedding booked 8-14 months out needs a long reverse-chronological checklist), and the framework section covers image optimization, mapping, and PDF generation.
When to use it
- You're building a venue marketplace and need discovery, booking, and planning designed as one system.
- You want map-based search with capacity, date, and budget filters laid out.
- You need a venue detail page with galleries, capacity breakdowns, and availability preview.
- You're designing an inquiry-to-booking flow with date holds, deposits, and e-signature contracts.
- You want a post-booking planning dashboard with vendor coordination and guest management.
- You need catering and menu selection plus day-of timeline tooling.
Example output
The model returns a feature-by-feature design document. Discovery is specified with card grids, a map view with price-labeled pins, quick filters, and a three-venue comparison table. The detail page covers categorized photo galleries, capacity breakdowns, and an availability calendar preview. The planning dashboard details a reverse-chronological timeline, a vendor coordination hub, guest list and RSVP tracking, and a budget tracker. The closing [framework] section adds responsive images with placeholders, a date-range picker with blackout dates, and PDF generation. Expect a detailed spec, not finished code.
Pro tips
- List
[venue_types]completely so the filters and capacity breakdowns match your real inventory (barns and rooftops imply different amenities). - Use
[lead_time]to calibrate the planning timeline — long wedding lead times need a 12-month-out checklist. - Set
[event_size]ranges so capacity filters and catering minimums are realistic. - Match
[event_types]to what you support; corporate galas and weddings need different inquiry questions. - Keep the availability-hold mechanic explicit (a 48-to-72 hour temporary hold) since it's central to booking.
- Ask the model to expand the planning dashboard if vendor coordination and the document vault matter most.
