Can I vibecode zcal?

Build a personalized, highly visual personal scheduling tool as a replacement for zcal's core features.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + SQLite + TailwindCSS + shadcn/ui.
Primary job: Build a brand-first scheduling tool that focuses on "Scheduling for the Receiver" with rich media integration, meeting polls, and calendar sync.

Core Features & Requirements:
1. Brand-First Booking Pages:
- Allow users to upload and display a welcome video or a cover photo on their booking page.
- Include custom branding options (custom fonts, colors) to make the page feel like a personal website rather than a utility.
- Add an introductory text section for personalized greetings.

2. Flexible Scheduling & Meeting Polls:
- Implement standard 1-on-1 booking flows that read availability from a connected calendar and write events back.
- Create a "Meeting Poll" feature (similar to Doodle) where organizers can propose multiple times and participants vote on the best option.
- Include logic for setting buffer periods, booking limits per day, and custom availability windows.

3. Technical & Architecture constraints:
- Start from an empty folder and create the complete working project.
- Make the default mode single-user and private.
- Store user data locally via SQLite.
- Do not add external analytics, telemetry, ads, or third-party accounts (besides OAuth for calendars).
- Put every secret and external credential in .env and provide .env.example.
- Use realistic sample data for testing the UI, including sample videos or images.
- Implement the smallest, most polished interface possible with clear empty, loading, validation, success, and failure states.

4. Security & Exclusions:
- Validate untrusted input and never log secrets or private file contents.
- Add import and export so the user is not trapped in the app.
- Use accessible keyboard navigation, labels, focus states, and sensible contrast.
- Deliberately exclude paid features like team routing, round-robin, and advanced external integrations (Stripe, Zapier, Google Analytics).
- Keep the app useful in a degraded mode if external APIs (like the calendar) fail or aren't connected yet.

5. Testing & Documentation:
- Write focused unit tests for the polling logic and availability calculation.
- Add one end-to-end smoke test that proves the booking flow works.
- Create a README with setup, permissions, architecture, data location, backup, and limitations.
- Add scripts for install, development, test, build, and a production-style local run.
- Run the tests and build before finishing, then fix errors rather than merely describing them.