Can I vibecode SavvyCal?

Build a collaborative, recipient-first scheduling substitute for SavvyCal in an empty repository.
Use exactly this stack: Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Google Calendar OAuth.
The primary job is to create a respectful booking experience that prioritizes the invitee's convenience while protecting the organizer's deep work time through ranked availability.

Core features to implement:
1. Ranked Availability Slots: Allow the organizer to configure their weekly availability by ranking time blocks (e.g., Rank 1 = Preferred, Rank 2 = Acceptable). The public booking interface should visually nudge invitees toward the highest-ranked slots.
2. Calendar Overlay Integration: Build a feature on the public booking page that allows a visitor to securely connect their own Google Calendar (read-only) and overlay their schedule on top of the organizer's availability to instantly spot mutual free time.
3. Intelligent Frequency Limits: Implement controls to cap the number of meetings per day or week, and force clustering of meetings to prevent calendar fragmentation.
4. Meeting Polls: Create a collaborative feature to propose multiple time slots for a group and collect votes before finalizing the event.
5. Core Booking Loop: Handle timezones robustly, create conflict-safe calendar events via Google Calendar API, and send confirmation emails with cancellation links.

Technical constraints:
- Server-rendered pages with Luxon for timezone math. Store data in PostgreSQL.
- Put every secret and external credential in .env and provide .env.example. Never log secrets.
- Re-check free/busy at submit time, not just render time, to prevent double booking.
- Do not add analytics, telemetry, ads, or third-party accounts. No accounts beyond the single user.
- Deliberately exclude paid features like integrated Stripe payments, team round-robin routing, and complex reminder sequences.
- Include clear empty, loading, success, and recoverable error states.
- Write focused tests for the ranked availability logic and the overlay synchronization.
- Create a README detailing the Google Cloud console OAuth steps and local setup instructions.