Can I vibecode lemcal?

Build a highly personalized, brand-first scheduling page substitute for Lemcal in an empty repository.
Use exactly this stack: Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Google Calendar OAuth.
The primary job is to create an ultra-customizable booking experience that feels like a natural extension of a personal brand, specifically designed to capture peak intent and reduce no-shows.

Core features to implement:
1. Brand-First Booking Page: Create a dynamic public page where I can embed a profile video (e.g., YouTube/Loom link), display social media widgets (like recent LinkedIn posts), and set custom background images (with Unsplash integration or custom URL). 
2. Seamless Calendar Integration: Connect to Google Calendar via OAuth to read free/busy times and write events back. Handle timezone detection automatically.
3. Custom Intake Forms: Add a lead qualification step where prospects must answer configurable questions before the booking is confirmed.
4. Booking Engine: Calculate availability, reserve slots transactionally to prevent double-booking, and create the calendar event.
5. Automated Reminders: Set up simulated endpoints for pre-meeting emails to reduce no-shows, leveraging the personalized brand identity.

Technical constraints:
- Make the default mode single-user and private.
- Store all user data locally. Put every secret and external credential in .env and provide .env.example.
- Do not add analytics, telemetry, ads, or third-party accounts.
- Implement the smallest polished interface that completes the core loop end to end, with a strong emphasis on a premium, highly customized look and feel.
- Include clear empty, loading, validation, success, and failure states.
- Ensure accessible keyboard navigation, labels, focus states, and sensible contrast.
- Write focused unit tests for the data model and the most important workflow, plus one end-to-end smoke test.
- Deliberately exclude enterprise features like team round-robin routing, robust Zapier integrations, or native CRM syncing.
- Create a detailed README with setup, architecture, and limitations. Add scripts for install, development, test, build, and local run.