peek-travel

The discipline for reading and writing a platform's back-office data from an app built on this kit — reach the API only through the platform's official SDK (never raw HTTP/GraphQL against a live account), discover capabilities from the INSTALLED SDK (they're…

The inbound-events model for an app built on this kit — receiving and handling platform webhooks (something happened: a booking created/changed/cancelled, a waiver signed, etc.). Use when adding an endpoint that reacts to a platform event for waitlist,…

How to read ACME back-office data with the AcmeAccessService SDK (from @peektravel/app-utilities) — the concrete ACME capability surface and the data rules around it. Use when calling the ACME API (activities, which come from published event templates), and…

The concrete ACME embed + auth wiring — how a starter-kit app embeds inside the ACME iframe and authenticates every request with the brand-agnostic peek-auth JWT. Use when adding or changing an authenticated ACME API route, the token handshake, the embed…

How to receive and handle ACME webhooks in a starter-kit app — today that means the platform-agnostic install-status webhook (install/uninstall lifecycle), NOT booking/waiver parsers (those are peek-only). Use when adding or changing the endpoint that reacts…

How to read Connect&GO (cng) back-office data with the CngAccessService SDK (from @peektravel/app-utilities) — the concrete cng capability surface and the data rules around it. Use when calling the cng API (products/activities), and for cng's capability…

The concrete Connect&GO (cng) embed + auth wiring — how a starter-kit app embeds inside the cng iframe and authenticates every request with the brand-agnostic peek-auth JWT. Use when adding or changing an authenticated cng API route, the token handshake, the…

How to receive and handle Connect&GO (cng) webhooks in a starter-kit app — today that means the platform-agnostic install-status webhook (install/uninstall lifecycle), NOT booking/waiver parsers (those are peek-only). Use when adding or changing the endpoint…

Build UI that looks native to Peek Pro using Odyssey, Peek's design system of framework- agnostic <ody-*> web components (from @peektravel/app-utilities). Use when adding or styling any embedded view, rendering Odyssey components in React, wiring the…

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,…

How to register, configure, and ship an app built on this starter kit — the app.json manifest (extendables, the registry settings URL, App Store listing), the Peek Development Hub, environment variables and secrets (PEEK_APP_SECRET / PEEK_APP_ID /…

How to expose an app's key functionality as an MCP endpoint so the Peek Pro App Store's AI orchestrator can drive the app without opening its UI. Use when adding or changing the app's MCP endpoint, deciding which tools to expose, defining a tool's input…

How to read and write Peek Pro back-office data from this starter kit using the PeekAccessService SDK (from @peektravel/app-utilities). Use when calling the Peek API — listing products/activities, querying availability/timeslots, reading or searching…

How this starter kit embeds inside the Peek Pro iframe and authenticates every request. Use when adding or changing an authenticated API route, a client-side data fetch, the token handshake, the install/embed entry route, CSP/iframe headers, or when debugging…

How to receive and handle Peek Pro webhooks (booking events and waiver events) in this starter kit. Use when adding an endpoint that reacts to something happening in Peek — a booking created/changed/cancelled, a waiver signed — for waitlist,…

How to test an app built on this starter kit and keep the suite meaningful — the Vitest setup already wired here, what to prioritize (auth/token handling, webhook state-not-change derivation, ID normalization, installDataId scoping), and the coverage…

Backport latest commits from phoenix_starter_kit into this project. Use when you need to sync upstream starter kit changes.

Check and increase test coverage to 100%. Use when coverage is below 100% or after writing new code. Identifies uncovered files, writes tests one file at a time, and repeats until fully covered.

Rules and checks for keeping this n8n community node package compliant with the n8n submission review. Use whenever adding or editing a node, a codex (.node.json) file, a resource/action, or the package.json n8n block — anything that would be re-reviewed on…