Booking kit: own availability, confirmations, and the agent loop

UpdatedSeptember 11, 2026

Scheduling links are excellent at one job: put a bookable calendar in front of a visitor, collect a slot, and drop a meeting onto someone's calendar. That loop is real for sales demos and one-off consults.

It is the wrong system of record when the appointment is the product. Coaches, therapists, stylists, and tutors need discovery, priced services, live availability, payment at confirm time, and client history on phone and web — inside an app they brand and keep changing. Renting someone else's booking UI forever leaves that surface on a vendor domain.

The booking-kit (Cadence) answers that narrower job. You already use a filesystem agent such as Cursor or Claude Code. You need appointment flows you own, staying as ordinary source in a repository your agents can extend.

This is an excerpt. Read the full post at otf-kit.dev/blog/booking-kit-own-the-repo — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

#kits #agents #architecture

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Rolling deploys on an owned backend: health checks, drain, and rollback

A restart is not a deploy. If you own the process, the load balancer, and the artifact, a production ship is a cutover: new instances must prove they can serve, old instances must stop taking work wit

Sep 21, 20261 min read

Rolling deploys on an owned backend: health checks, drain, and rollback

Postgres connection pooling after sandbox exit so concurrent AI traffic cannot melt the DB

After you leave a Lovable or Bolt sandbox and own the backend, every agent turn, tool call, and concurrent request can open a fresh Postgres session. Sandbox hosts often hide that cost behind a shared

Sep 21, 20261 min read

Postgres connection pooling after sandbox exit so concurrent AI traffic cannot melt the DB

Timed database restore drills into an isolated target prove RTO and RPO

After you leave a Lovable or Bolt sandbox and own the backend, a backup file sitting in object storage is not a recovery plan. Recovery is a timed restore drill: restore into an isolated target, prove

Sep 20, 20261 min read

Timed database restore drills into an isolated target prove RTO and RPO

Audit trail events for SaaS ops: append-only who-did-what you can query

When support asks “who changed this plan?”, noisy app logs rarely answer. They show request latency, stack traces, and correlation IDs — useful for triage, weak for accountability. After you leave a L

Sep 20, 20261 min read

Audit trail events for SaaS ops: append-only who-did-what you can query

API timeouts and retries when your app calls AI backends you own

When your owned app calls a model or AI HTTP API, the client timeout budget and retry policy live in your code — not in a sandbox dashboard. Sandbox builders (Lovable, Bolt, and similar) often hide co

Sep 20, 20261 min read

API timeouts and retries when your app calls AI backends you own

OTF — kits your AI coding agent can ship to production

622 posts

Engineering notes on shipping production apps with AI coding tools — Claude Code, Cursor, Codex, Lovable, Bolt — and the stack underneath: React Native, Expo, Next.js, Supabase. Honest takes on what works, what breaks, and the full-stack kits that get you to production faster. By OTF.

Command Palette

Comments

More from this blog