timerise-ai

Booking Kiosk — Development skill for Claude Code

Development community

Agent Skill: build a self-service touchscreen booking kiosk — seven-step walk-up flow, on-screen keyboard, inactivity auto-reset, server-priced bookings with capacity transactions and stock locks, pay.

How to install Booking Kiosk

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerise-ai/booking-kiosk and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Booking Kiosk does

Agent Skill: build a self-service touchscreen booking kiosk — seven-step walk-up flow, on-screen keyboard, inactivity auto-reset, server-priced bookings with capacity transactions and stock locks, pay-at-counter or pay-by-QR, live availability refresh, LAN offline failover, find-my-booking edit — in Next.js App Router, backend-agnostic

Alternatives in Development

  • Sprint Plan — Plan sprints with capacity, story selection, and risk mapping 7.8k ★
  • Ecpay Pay — 串接綠界金流收款(AIO / 站內付 2.0 / 幕後授權)、查詢訂單、退款、Callback 處理 169 ★
  • Accumulate Csvs — Accumulate monthly merged transactions into a cumulative yearly dataset 90 ★

README

booking-kiosk

An [Agent Skill](https://agentskills.io) that teaches an agent to build a self-service touchscreen booking kiosk in a **Next.js App Router** app — a seven-step walk-up flow (service → date → time slot → stations and participant names → equipment and consumables → summary → confirmation) with an on-screen keyboard, inactivity auto-reset, pay-at-counter or pay-by-QR, live availability refresh, and a find-my-booking edit flow. Backend- and payment-provider-agnostic.

A kiosk is a booking website with the trust model inverted. The client is unauthenticated by design and physically shared by strangers, so **all trust lives on the server** — prices, capacity, promo validity, idempotency — and **all state is disposable**: in memory, auto-reset, never persisted, because the next customer must not see the previous one's name. Everything in this skill follows from those two facts.

It is extracted from a production venue-booking system where the kiosk ran as one of five surfaces sharing a booking engine at a multi-location venue with a LAN fallback server. The state machine, screen flow, timers, stock model, capacity transaction and offline failover are proven there — but the templates are the **hardened** version, not a copy: a three-pass audit found twelve defect clusters, including device auth that a *missing* header walked straight through and Stripe amounts computed from client-supplied prices. [`references/provenance.md`](references/provenance.md) names every one, and separates what was fixed, what was kept deliberately, and what was designed here and has never run in production.

Install

One command, via the [skills.sh](https://www.skills.sh) CLI, which installs the skill into every skills-compatible agent it detects — Claude Code, Codex CLI, Gemini CLI and others:

npx skills add timerise-ai/booking-kiosk

Name the agents instead with `-a`, for example `npx skills add timerise-ai/booking-kiosk -a claude-code -a codex`.

Or clone it you