Can I vibecode Vimcal?

Build a blazing-fast, keyboard-first personal replacement for Vimcal in an empty repository.
Use exactly this stack: Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks.
Primary job: Build a high-performance scheduling layer designed for power users that integrates with Google Calendar, focusing on speed, keyboard shortcuts, and seamless time-zone management.

Core Requirements & Architecture:
- Implement a unified calendar view that is heavily reliant on keyboard shortcuts (e.g., 'c' to create, 't' to jump to today, 'j/k' to navigate days) to minimize mouse usage.
- Build a "Time Travel View" that visually compares overlapping working hours across multiple time zones, making scheduling for distributed teams effortless.
- Create a drag-and-drop availability sharing feature ("Slots") that generates a personalized text snippet of open times to paste into emails, rather than just a rigid booking link.
- Develop a basic Natural Language Processing (NLP) parser for event creation (e.g., typing "Coffee tomorrow at 10am with Alex" automatically populates the form).
- Provide a clean, minimal interface that prioritizes speed and reduces "calendar fatigue".
- Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.

Technical Constraints:
- Make the first run work locally with one documented command.
- Store all user data locally by default and make export straightforward.
- Put secrets in .env, ship .env.example, and never commit credentials.
- Calculate availability in UTC and render it in the visitor's detected timezone accurately.
- Send confirmation and reminder emails via Resend.
- Add input validation, safe filenames, and graceful handling of unavailable APIs.

Deliberate Exclusions:
- Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
- Deliberately leave out Microsoft and Apple calendar support, and team round-robin routing.
- Do not fake proprietary data, model quality, compliance, or security claims.

Testing & Documentation:
- Write focused tests for the NLP parsing, timezone calculations, and core transformation logic.
- Add one end-to-end happy path test.
- Create a comprehensive README with setup, architecture, permissions, data location, and backup steps.
- Finish by running the tests and listing the exact commands used.