Vimcal?

Build a focused replacement for Vimcal for an independent professional booking one type of appointment, based on this public product description: “Vimcal | Fastest Calendar for People with Too Many Meetings — Vimcal is the world’s fastest calendar, beautifully designed for people who have too many meetings. Drag to share availabilities, schedule across time zones, and see all your Outlook and Google calendars in one view.” Do not copy the original brand, proprietary assets, name, logo, UI, or copy; create an original visual system.

Core workflow
- Recreate only the narrow primary workflow described above, with define availability, timezone, duration, buffer, and booking questions; show a public booking page with conflict-safe reservation; send or display confirmation and cancellation state; include calendar-provider adapter boundaries and exportable bookings.
- Keep the product name and source description in a research note in the README, and turn every uncertain behavior into an explicit assumption or user setting rather than inventing a feature.
- Use a small React/TypeScript app with a portable JSON or SQLite data model, clear loading/empty/error states, and adapters around external services. Seed realistic demo data so the complete workflow works without paid credentials.

Scope boundaries
- Out of scope for v1: multi-provider enterprise scheduling; payments and complex routing; guaranteed calendar consistency without a provider. Do not promise feature parity, proprietary data, or enterprise reliability.

Include a README with setup, environment variables, data model, implementation decisions, privacy behavior, testing instructions, and important limitations.