Appointment booking app prompt for service businesses

Build an appointment booking app for [BUSINESS TYPE]. Customers book [SERVICE TYPES] in [BUSINESS TIME ZONE]. Staff need to manage [STAFF COUNT] calendars. The core promise is that a confirmed slot cannot be booked twice.

First explain the rules for service duration, buffers, opening hours, staff availability, blackout dates, lead time, cancellation cutoff, and capacity. Ask for any missing rule. Then build:
1. A public service selector with duration, price or quote status, and clear eligibility notes.
2. A calendar that displays only available times in the customer's local time zone while storing times consistently. Show the business time zone at confirmation.
3. A short booking form with necessary contact fields, accessible validation, and a final review step.
4. Confirmation, reschedule, and cancellation states with a unique booking reference.
5. A staff view for daily appointments, blocked time, manual booking, and status changes.

Reliability requirements:
- Reserve availability atomically on the server; recheck the slot at submission and explain a conflict without losing form data.
- Treat daylight-saving changes and overnight boundaries explicitly. Never infer availability solely from what the browser displayed earlier.
- Send confirmation or reminder messages only when an email/SMS integration is configured. Otherwise label the message as a preview and provide the integration task.
- If [PAYMENT POLICY] requires payment, show a clear integration boundary and do not mark a booking paid without a verified payment event.
- Use sample bookings that are clearly fictional. Protect customer contact details from public access.

Design for mobile thumb use, keyboard navigation, clear focus, and useful empty and error states. Finish by testing two customers selecting the same last slot, a canceled slot becoming available again, and a booking across a daylight-saving change.