Can I vibecode Zoho Bookings?

Build a robust, resource-aware appointment scheduling tool as a personal substitute for Zoho Bookings.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + SQLite + TailwindCSS + shadcn/ui.
Primary job: Build an appointment scheduling tool that not only handles personal time but also manages physical resources (rooms, equipment) and multi-department categorization.

Core Features & Requirements:
1. Resource & Workspace Management:
- Expand the standard scheduling model to require a "Resource" (e.g., Meeting Room A, Projector) in addition to time availability.
- Implement a conflict-checking system that ensures both the host's time AND the required physical resource are available before confirming a booking.
- Allow grouping meeting types into "Workspaces" or "Departments" (e.g., Sales, Support) for a clean, categorized public booking page.

2. Customizable Booking & Workflows:
- Create branded booking pages with customizable logos, colors, and backgrounds.
- Provide a smooth self-scheduling experience for customers with automatic timezone conversion.
- Build a unified admin dashboard to view upcoming appointments, manage resources, and manually schedule or cancel bookings.

3. Calendar Integration:
- Read availability from a single primary calendar and write confirmed events back.
- Allow setting custom work hours, buffer times, and specific availability windows per event type.

4. Technical & Architecture Constraints:
- Start from an empty folder and create the complete working project.
- Make the default mode single-user (one host, multiple resources).
- Store user data locally via SQLite.
- Put every secret and external credential in .env and provide .env.example.
- Implement a polished interface with accessible keyboard navigation, clear error states, and responsive design.

5. Exclusions & Limitations:
- Deliberately exclude Zoho's paid enterprise features: large team round-robin, deep CRM integrations, complex payment gateways, and advanced automated SMS workflows.
- Do not add analytics, telemetry, or third-party tracking.
- Do not fake proprietary AI setup tools or integrations.

6. Testing & Documentation:
- Write focused unit tests for the dual-conflict resolution logic (host time + resource availability).
- Add one end-to-end smoke test that proves a resource-constrained booking works.
- Create a README with setup instructions, architecture overview, and local run commands.
- Run the tests and build before finishing, fixing any errors along the way.