Vibecode TidyCal
track this build5 steps, step by step0%KINDA · weekend project
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For TidyCal, publish simple booking pages connected to one calendar and send confirmations. The hard boundary is lifetime hosted service, calendar integrations, and extremely low maintenance cost, plus calendar integrations and reliability.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of TidyCal. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # TidyCal indie build ## Goal Build the smallest trustworthy replacement for the core TidyCal workflow for one developer or a tiny team. ## Scope Read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - lifetime hosted service, calendar integrations, and extremely low maintenance cost - multiple calendar providers - team routing and round-robin - payments - timezone edge-case maturity If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a personal replacement for TidyCal in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks. The core loop is: read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. 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. Implement one account with configurable working hours, buffers, minimum notice, and booking horizon. Connect Google Calendar using OAuth and store refresh tokens encrypted at rest. Calculate availability in UTC and render it in the visitor's detected timezone. Reserve slots transactionally, create calendar events, and prevent concurrent double booking. Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out Microsoft and Apple calendar support. Deliberately leave out team round-robin routing. Deliberately leave out payments, CRM workflows, and enterprise controls. Finish by running the tests and listing the exact commands used. ## Required capabilities - Google Calendar OAuth credentials - PostgreSQL - public deploy target - Resend API key - domain with HTTPS ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of TidyCal. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # TidyCal indie build ## Goal Build the smallest trustworthy replacement for the core TidyCal workflow for one developer or a tiny team. ## Scope Read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - lifetime hosted service, calendar integrations, and extremely low maintenance cost - multiple calendar providers - team routing and round-robin - payments - timezone edge-case maturity If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a personal replacement for TidyCal in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks. The core loop is: read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. 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. Implement one account with configurable working hours, buffers, minimum notice, and booking horizon. Connect Google Calendar using OAuth and store refresh tokens encrypted at rest. Calculate availability in UTC and render it in the visitor's detected timezone. Reserve slots transactionally, create calendar events, and prevent concurrent double booking. Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out Microsoft and Apple calendar support. Deliberately leave out team round-robin routing. Deliberately leave out payments, CRM workflows, and enterprise controls. Finish by running the tests and listing the exact commands used. ## Required capabilities - Google Calendar OAuth credentials - PostgreSQL - public deploy target - Resend API key - domain with HTTPS ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of TidyCal. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # TidyCal product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For TidyCal, publish simple booking pages connected to one calendar and send confirmations. The hard boundary is lifetime hosted service, calendar integrations, and extremely low maintenance cost, plus calendar integrations and reliability. ## Product outcome Read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth credentials - PostgreSQL - public deploy target - Resend API key - domain with HTTPS ## Explicit non-goals for v1 - lifetime hosted service, calendar integrations, and extremely low maintenance cost - multiple calendar providers - team routing and round-robin - payments - timezone edge-case maturity ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a personal replacement for TidyCal in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks. The core loop is: read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. 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. Implement one account with configurable working hours, buffers, minimum notice, and booking horizon. Connect Google Calendar using OAuth and store refresh tokens encrypted at rest. Calculate availability in UTC and render it in the visitor's detected timezone. Reserve slots transactionally, create calendar events, and prevent concurrent double booking. Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out Microsoft and Apple calendar support. Deliberately leave out team round-robin routing. Deliberately leave out payments, CRM workflows, and enterprise controls. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted TidyCal capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# TidyCal indie build ## Goal Build the smallest trustworthy replacement for the core TidyCal workflow for one developer or a tiny team. ## Scope Read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - lifetime hosted service, calendar integrations, and extremely low maintenance cost - multiple calendar providers - team routing and round-robin - payments - timezone edge-case maturity If those capabilities are essential, use Cal.com instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a personal replacement for TidyCal in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks. The core loop is: read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. 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. Implement one account with configurable working hours, buffers, minimum notice, and booking horizon. Connect Google Calendar using OAuth and store refresh tokens encrypted at rest. Calculate availability in UTC and render it in the visitor's detected timezone. Reserve slots transactionally, create calendar events, and prevent concurrent double booking. Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out Microsoft and Apple calendar support. Deliberately leave out team round-robin routing. Deliberately leave out payments, CRM workflows, and enterprise controls. Finish by running the tests and listing the exact commands used. ## Required capabilities - Google Calendar OAuth credentials - PostgreSQL - public deploy target - Resend API key - domain with HTTPS ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# TidyCal product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For TidyCal, publish simple booking pages connected to one calendar and send confirmations. The hard boundary is lifetime hosted service, calendar integrations, and extremely low maintenance cost, plus calendar integrations and reliability. ## Product outcome Read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth credentials - PostgreSQL - public deploy target - Resend API key - domain with HTTPS ## Explicit non-goals for v1 - lifetime hosted service, calendar integrations, and extremely low maintenance cost - multiple calendar providers - team routing and round-robin - payments - timezone edge-case maturity ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a personal replacement for TidyCal in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks. The core loop is: read one calendar, publish simple booking pages with availability, create conflict-safe bookings, and send confirmations and reminders. 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. Implement one account with configurable working hours, buffers, minimum notice, and booking horizon. Connect Google Calendar using OAuth and store refresh tokens encrypted at rest. Calculate availability in UTC and render it in the visitor's detected timezone. Reserve slots transactionally, create calendar events, and prevent concurrent double booking. Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out Microsoft and Apple calendar support. Deliberately leave out team round-robin routing. Deliberately leave out payments, CRM workflows, and enterprise controls. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted TidyCal capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
People still pay for TidyCal because people pay because one double booking or missed invite can cost more than years of subscription fees. The recurring cost buys OAuth refresh, webhooks, timezone databases, race conditions, reminders, deliverability, privacy, and uptime, not just the visible interface.
xlifetime hosted service, calendar integrations, and extremely low maintenance cost
xmultiple calendar providers
xteam routing and round-robin
xpayments
xtimezone edge-case maturity
share on X ↗"I just replaced TidyCal with one prompt"
Don't feel like building it? These folks already made it free.
Cal.com FreeUnlimited solo event types, calendars and bookings, with payments and notifications; team routing costs money.free↗
Calendly FreeOne active event type and unlimited bookings; meeting polls survive, workflows and teams do not.free↗
Google Calendar appointment schedulesOne bare appointment page inside the calendar you already use; reminders, payments and polish are paid.free↗all 6 free alternatives to TidyCal →· no votes, no pay-to-list · just what's real
TidyCal pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0 | $0 | Unlimited bookings and booking types; 1 readable calendar connection and 1 writable calendar; paid, recurring, and package bookings. |
| individual lifetime | custom | — | 10 calendar connections; group bookings; AI assistant; custom emails and analytics. |
| agency lifetime | custom | — | 25 calendar connections; unlimited team members; round-robin and collective meetings; US/Canada SMS reminders. |
| pro | $12 | $8.25 | 25 calendar connections; no TidyCal branding; custom domain; priority support. |
free tierUnlimited bookings and booking types; 1 readable calendar connection and 1 writable calendar; paid, recurring, and package bookings.
billingFree forever + one-time lifetime licenses + Pro monthly or annual (-31%)
hidden costsPayment processing still costs extra; Agency retains reduced TidyCal branding, while complete branding removal requires Pro.
verified 2026-08-14 · source ↗
Vibecode TidyCal
Kinda. The core of TidyCal is buildable in a weekend with the prompt on this page, but there are real gaps: lifetime hosted service, calendar integrations, and extremely low maintenance cost, multiple calendar providers. Read the honest list above before committing.
How much does TidyCal cost?
TidyCal's pricing is usage-based or varies by plan · Sold as a one-time AppSumo-style lifetime purchase; canonical monthly price is null..
What do I lose by replacing TidyCal?
Honestly: lifetime hosted service, calendar integrations, and extremely low maintenance cost; multiple calendar providers; team routing and round-robin; payments; timezone edge-case maturity. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to TidyCal?
Yes: Cal.com Free (Unlimited solo event types, calendars and bookings, with payments and notifications; team routing costs money.) Calendly Free (One active event type and unlimited bookings; meeting polls survive, workflows and teams do not.) Google Calendar appointment schedules (One bare appointment page inside the calendar you already use; reminders, payments and polish are paid.) All 6 curated free alternatives are at vibecodeit.com/tidycal/alternatives. The prompt is for when you want it exactly your way.