Menu
SkillsMP has collected 30 skills from peek-travel/app-cli. Open a skill to review its source and details.
Showing 30 of 30 collected skills.
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…
How to read and write Peek Pro back-office data with the PeekAccessService SDK (from @peektravel/app-utilities) — the concrete Peek capability surface and the data rules around it. Use when calling the Peek API (products/activities, availability/timeslots,…
The concrete Peek Pro embed + auth wiring — how a starter-kit app embeds inside the Peek Pro iframe and authenticates every request with a peek-auth JWT. Use when adding or changing an authenticated API route, a client-side data fetch, the token handshake,…
How to receive and handle Peek Pro webhooks (booking, waiver, and install/uninstall lifecycle events) in a starter-kit app — the concrete Peek delivery, registration/config split, and parsers. Use when adding an endpoint that reacts to something happening in…
The @peektravel/app-utilities package — the JavaScript SDK for apps on the Peek platform (peek, cng, and soon acme). Use when importing from @peektravel/app-utilities, calling the back-office API clients, wiring Odyssey UI, or parsing webhooks — and,…
Build UI with Odyssey, the shared app design theme of framework-agnostic <ody-*> web components shipped inside @peektravel/app-utilities. Use when adding or styling any embedded view, rendering Odyssey components in React, wiring the OdysseyLoader, finding…
The host-owned-identity auth model for an app embedded in a platform's back-office surface, and how to authenticate every request. Use when adding or changing an authenticated API route, a client-side data fetch, the token handshake, the embed entry route,…
The Peek app CLI (@peektravel/app-cli) — the tool that connects your local app to the app registry: discovering commands, checking which registry you're on (production vs sandbox) and who you're logged in as, running the app locally behind a Cloudflare tunnel…
The concrete ACME MCP endpoint — how a starter-kit app exposes its functionality as MCP tools for the App Store AI orchestrator, on ACME. Use when adding or changing the app's ACME MCP endpoint, wiring its auth, or declaring it in app.acme.json. Covers…
The concrete Connect&GO (cng) MCP endpoint — how a starter-kit app exposes its functionality as MCP tools for the App Store AI orchestrator, on cng. Use when adding or changing the app's cng MCP endpoint, wiring its auth, or declaring it in app.cng.json.…
The concrete Peek manifest, registration, and deploy — how to register, configure, and ship a starter-kit app to a Peek Pro account. Covers the app.json manifest (extendables, the registry settings URL that is the embed URL Peek POSTs to), the…
The concrete Peek MCP endpoint — how a starter-kit app exposes its functionality as MCP tools so the Peek Pro App Store's AI orchestrator can drive it without opening the UI. Use when adding or changing the app's MCP endpoint, wiring its auth, or declaring it…
How to register, configure, and ship an app built on this kit — the manifest that declares the app to the platform registry, registration in the platform's developer hub (app id + shared secret, sandbox before prod), environment variables and secrets, and…
Concrete recipe for deploying a Next.js app built on this kit to Fly.io — flyctl login, launching into a shared org, the pnpm-workspace Dockerfile gotcha that breaks the auto-generated build, and attaching a managed Postgres. Use when the chosen host is…
Entry point and guided workflow for building an app that extends a booking/commerce platform on this CLI's starter kit — an app that embeds inside the platform's back-office surface. Use when the user wants to build a platform app or add a feature to one —…
How to adjust Peek Pro ticket prices from your app with the pricing engine + overrides API on PeekAccessService (from @peektravel/app-utilities). Use when building dynamic/scheduled/tiered pricing — promos, group discounts, demand- or time-of-day-based…
The concrete ACME manifest, registration, and deploy — how to register, configure, and ship a starter-kit app to an ACME account. Covers app.acme.json (the acme_backoffice_api@v1 platform extendable, the app_registry_settings_url that is the embed URL ACME…
The concrete Connect&GO (cng) manifest, registration, and deploy — how to register, configure, and ship a starter-kit app to a cng account. Covers app.cng.json (the cng_backoffice_api@v1 platform extendable, the app_registry_settings_url that is the embed URL…
How to expose an app's key functionality as an MCP endpoint so the 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 schema, or…
Testing discipline for an app built on this kit — what to prioritize (the critical integration logic where bugs hide: auth/token handling, webhook "state not change" derivation, ID normalization, per-install data scoping, env validation), preferring behavior…
The Next.js / App-Router stack facts for apps built on this kit — treat it as "not the Next.js you know," read the installed docs, and follow the kit's route-handler, client-SPA, CSP, runtime, and env-validation patterns. Use when adding or changing a route…
The test tooling for JS-stack apps on this kit — Vitest with v8 coverage, colocated __tests__/ folders, and the lint→typecheck→test→build CI gate. Use when adding tests, running the suite, checking coverage, wiring the @/ alias, or debugging CI. This skill is…
How to type custom elements (web components like Odyssey's <ody-*>) for React/TSX by augmenting JSX.IntrinsicElements. Use when adding or editing a custom-element declaration, when a JSX attribute or ref on a custom element won't type-check, or when tsc…