timerise-ai

Bookable Events — Development skill for Claude Code

Development community

Agent Skill: build bookable events with Stripe payments and anti-no-show card holds: capacity-limited registration, Stripe Checkout tickets, deposits released on check-in and captured on no-show, staf.

How to install Bookable Events

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

What Bookable Events does

Agent Skill: build bookable events with Stripe payments and anti-no-show card holds: capacity-limited registration, Stripe Checkout tickets, deposits released on check-in and captured on no-show, staff check-in, refunds, event cancellation, idempotent webhooks, in Next.js App Router on Firestore or Postgres

Alternatives in Development

  • Project-Level Skills — This directory contains skills for developing and maintaining the claude-mem project itself, not skills that a 39.3k ★
  • Stripe — Payments Stripe integration with best-practices skill 14k ★
  • Sprint Plan — Plan sprints with capacity, story selection, and risk mapping 7.8k ★

README

bookable-events

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to build **bookable events with Stripe payments and anti-no-show deposits** in a **Next.js App Router** app: capacity-limited registration for free and paid events, Stripe Checkout tickets, a refundable card hold on free events that is released when the guest checks in and captured when they don't show, staff check-in, refunds and event cancellation. Firestore or Postgres; any ISO currency, USD by default.

Events are the easy half. The hard half is money moving while seats are scarce: a seat taken before payment, a payment that lands after the seat expired, a card hold that lapses before a no-show can be charged. The skill runs **every change through one pure state machine inside a database transaction, and calls Stripe only after commit**. A durable intent (`RELEASING`, `CAPTURING`, `REFUND_PENDING`) is left behind, and a single five-minute tick retries it with the same idempotency key until Stripe confirms.

This skill was written by the engineer who has shipped this module. The earlier implementation it was audited against was the events module of a multi-location venue-booking system. The templates hold the properties such a module has to hold: a paid event is never free in a currency it has no price in; a declined attempt inside open Checkout keeps the seat, and only session expiry releases