Underused Venue Marketplace

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "OffHours": a concierge-run marketplace that lists underused venues such as churches, gyms and clubs and lets planners request a booking. The operator onboards each venue; the owner approves requests. No payment or insurance flows through the app this weekend.
   
   Stack: Next.js (App Router, TypeScript), Tailwind, Supabase (Postgres with PostGIS, Row Level Security, Storage, Auth with email magic link), the Anthropic API to draft each listing. Listing pages are server-rendered for search. Deploy on Vercel.
   
   Tables (Row Level Security on; hosts read and write their own venues and requests, live venues and spaces are public):
   - venues(id, owner_user_id, name, type, address, lat, lng, city, description, status) type is worship, fitness, club, community or other; status is draft, live or paused
   - spaces(id, venue_id, name, capacity_seated, capacity_standing, square_feet, hourly_rate_cents, minimum_hours, amenities jsonb, photos jsonb)
   - house_rules(id, venue_id, no_alcohol boolean, no_amplified_music_after, restricted_areas text[], custom_terms)
   - availability_rules(id, space_id, kind, weekday, start_time, end_time, start_date, end_date) kind is recurring_block, one_off_block or open_window
   - booking_requests(id, space_id, guest_user_id, starts_at, ends_at, headcount, declares_alcohol boolean, declares_music boolean, status)
   
   Screens: /login, /[city] (browse), /space/[id] (listing), /request/[spaceId], /host (requests and calendar), /admin/intake (the operator's mobile form).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), ANTHROPIC_API_KEY.
   
   Do not build: billing or commissions, payments or payouts, event insurance, reviews and damage claims, a cancellation policy, SMS.
   Done when: npm run dev starts, you can sign in, and the five tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves OffHours: a calendar that is never wrong, a search that never shows a listing that will refuse, and an intake tool that makes each listing good.
   1. Write availability as a pure function: given a space and a requested range, start from its open windows (all hours if none), subtract recurring blocks for that weekday, subtract one-off blocks that overlap, subtract confirmed requests with a 60-minute buffer on each side, and reject a result shorter than the minimum hours. Return the free intervals, not a yes or no. Unit test daylight saving changes, overnight bookings and back-to-back requests.
   2. Search on /[city] filters by time range, headcount, maximum hourly rate, venue type, amenities and distance from a point. Rank by availability match, then a completeness score (photos, description length), then distance. Do not rank by price. If the guest declares alcohol or amplified music, hide any venue whose house rules forbid it.
   3. A guest sends a booking request for a time range. Re-check availability when the host approves, not only when the guest sends. The host approves or declines and the status changes.
   4. The operator's /admin/intake is a mobile form: venue basics, a guided 12-photo shot list with a reference thumbnail for each that blocks saving until all 12 are taken, the recurring in-use blocks, blackout dates, restricted areas, the alcohol policy, the noise cutoff and capacity.
   5. Draft the listing with the Anthropic API from the answers and the photo captions: 120 words, leading with the most distinctive physical feature, stating capacity and what is included, naming two event types it fits and one it does not. Reject any draft containing "stunning", "nestled", "perfect for any occasion" or "state-of-the-art" and regenerate once.
   6. Suggest an hourly rate as the median of completed requests in the same city, type and capacity band, with the sample size. With fewer than 5 comparables, say so and use the rate the operator types.
   Rules: say on every request page that payment and insurance are arranged between guest and host outside the app. Never double-book.
   Empty state: a city with no venues shows the operator's contact form.
   Done when: the availability tests pass, a guest declaring alcohol never sees a venue that forbids it, an approval is refused if another request took the time first, the intake blocks with 11 photos and a banned word triggers a regeneration.

3. 3. Landing Page

   Build a one-page landing site for OffHours, bookable event space in places that sit empty most of the week.
   Hero: "Event space in the buildings your city already has." Sub: "Churches, gyms and clubs with open hours, listed by people who visited each one. Request a time and the owner confirms." Two buttons: Join the waitlist as a planner, Join as a venue owner.
   Sections: the problem (planners cannot find space and venues sit empty), how it works in four steps (we visit, rules are written down, you request, the owner confirms), a sample listing with house rules and an FAQ on payment and insurance today (arranged between you and the host) and which city comes first.
   Waitlist: store the email and the role in a waitlist table in Supabase. No other service.
   Style: Geist, a warm off-white background, one deep green accent, photography as the main visual.
   Done when: the page renders on a phone and a submitted email with its role appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for OffHours: a wordmark and an icon that suggest a door slightly ajar with a clock face as its window.
   Colors: warm off-white, deep ink and one deep green. Type: Geist, with tabular numbers for hours and rates.
   Deliverables: wordmark, icon, three request status chips (pending, approved, declined) that differ by shape as well as color, a listing card layout, and one launch graphic.
   Done when: each deliverable is saved in one folder and the status chips are distinguishable without color.