Calendly

Promptfree, for everyone, and the only version there is

Open the prompt in Claude CodeOpen the prompt in CodexOpen the prompt in Cursor

Copy

Build me a booking page I run myself: someone picks a slot, it lands in my calendar, and neither of us emails about it.

STACK
- Astro with a Node adapter, server-rendered HTML, no frontend framework
- SQLite via better-sqlite3, one file, WAL mode
- Google Calendar over OAuth for the calendar side
- SMTP from environment variables for mail

EVENT TYPES
- Defined in a config file, not a database table: name, slug, duration, buffer before and after, minimum notice, and how many days ahead can be booked
- Weekly availability windows written in my own timezone, plus a list of dates I am unavailable
- More than one event type, each on its own URL

THE BOOKING PAGE
- Public, no account, works without JavaScript for the choosing and the submitting
- Slots rendered in the visitor's timezone, detected from the browser and changeable with a visible picker
- A slot is never shown unless it can actually be honoured — check the calendar at render time and again at submit time
- Name, email and one free-text field; nothing else

CALENDAR
- Read busy blocks with the free/busy query and treat that as the only source of truth for conflicts
- Write the confirmed event with both parties as attendees and the meeting link in the body
- Reconnect cleanly when the OAuth token expires, and say so on screen rather than failing silently

TIME, WHICH IS WHERE THIS GOES WRONG
- Every calculation in UTC, with an explicit IANA conversion at the edges only
- Unit tests covering: a DST transition in both directions, a booking that crosses midnight, a visitor in a half-hour offset zone such as Asia/Kolkata, and a slot that becomes unavailable between render and submit

AFTER THE BOOKING
- Confirmation, reschedule and cancel links signed with an HMAC token, so no account is needed and no link can be guessed
- Confirmation email with an ICS attachment that opens correctly in Apple Calendar, Outlook and Google
- A reminder the day before, sent by a cron job that is safe to run twice

DATA
- Every booking stored append-only: a cancellation is a new row, never a delete
- A single admin page listing what is coming up, read from that history

Include a README covering the Google OAuth setup, the SMTP variables, and how to add an event type.