peek-app-builder

name

peek-app-builder

description

Entry point and guided workflow for building an app on this Peek Pro starter kit (a Next.js app that embeds inside Peek Pro's back-office iframe). Use when the user wants to build a Peek Pro app or add a feature to one — waitlist, abandoned-booking recovery, dynamic pricing, custom checkout, reseller/channel sync, reporting, webhook handling, or anything Peek Pro lacks natively. Owns the discover → mock → plan → sign-off → build → validate flow and delegates the specifics to the peek-embed-and-auth, peek-backoffice-api, peek-webhooks, peek-mcp-endpoint, odyssey-ui, peek-app-manifest-and-deploy, and testing-peek-apps skills. Triggers on "Peek Pro app", "PeekPro", "Peek app", "Peek booking", "Peek integration", "build on the starter kit".

Build a Peek Pro app (on this starter kit)

You are helping the user build an app that extends Peek Pro — a tours & activities booking platform — using this repository, an opinionated Next.js starter kit that already ships the hard parts (iframe embed, the auth pipeline, the Peek SDK client, Odyssey UI, tests, CI). Your job is to extend what's here, not rebuild it from scratch.

Peek Pro is sparsely documented, so do not rely on model memory for Peek specifics. These skills carry the canonical knowledge and tell you when to look things up live.

The core stack is already decided — don't re-litigate it

Unlike a greenfield build, you do not choose the language, framework, or SDK. This kit is Next.js 16 + React 19 + Tailwind 4 + TypeScript (App Router), tests with Vitest, and talks to Peek through the @peektravel/app-utilities package (PeekAccessService, Node-only — the first-class SDK). Take these as given.

Host and database are still your choice (the "moving layer" — see below). The recommended default is Vercel for hosting and Neon (serverless Postgres) for data when you need it, accessed (a ), with live UI via polling/SSE from your own API routes — offer it as a recommendation, not a mandate. Phase 0 ships (persistence is deliberately deferred), so most first apps don't need one yet. See for the deploy/secrets specifics — including (its auth/RLS model doesn't match Peek's token).