# AGENTS.md — Build guide for FareHarbor ## Project scope Define tour departures with seat capacity, hold seats during checkout and provide staff with a check-in manifest and explicit cancellation/refund states. Catalogue verdict: kinda. The part everyone thinks they are paying for, a calendar with capacity, a checkout, and a manifest the guides can read, is genuinely a weekend build with Stripe doing the hard money parts. The part that is actually load-bearing is everything after that: pushing live availability to Viator, GetYourGuide, Expedia and Booking.com, reconciling reseller commissions, handling refunds and chargebacks on other people's money, and a phone line that answers at 6am when the 7am kayak trip is double-booked. A self-hosted build replaces direct-website bookings cleanly and replaces channel distribution not at all. If most of your volume is direct and you can eat the ops burden, the maths gets interesting fast. If OTAs feed you, you are rebuilding a channel manager, which is not a weekend. Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope. ## Working agreement - Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture. - Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled. - After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran. - Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply. - Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization. ## Prerequisites - Runtime and tools: TypeScript, React, Node, PostgreSQL and hosted Stripe Checkout for one tour operator. - Before starting: A PostgreSQL database, departure/capacity examples, the operator timezone, a Stripe sandbox account with webhook setup and an authenticated staff role. ## Stack and architecture - TypeScript, React, Node, PostgreSQL and hosted Stripe Checkout for one tour operator - Data design: Store Tour, Departure, CapacityHold, Booking, Passenger and PaymentReceipt; active holds plus confirmed seats may never exceed capacity, and payment identity is deduplicated. - Setup: A PostgreSQL database, departure/capacity examples, the operator timezone, a Stripe sandbox account with webhook setup and an authenticated staff role ## Security and data integrity - Use transactional capacity holds against dated departures, not personal calendar free/busy. Store verified payment events and reconcile late/failed payments; confirmation requires capacity and payment state to agree. - Payment integration needs current provider webhook rules and a refund policy. Do not treat browser redirects as proof of payment or electronic waiver capture as legal enforceability. - Keep secrets outside client bundles and exported projects; document what leaves the device and make retention/deletion controls visible. ## Agent implementation rules - Project rule — domain: Store Tour, Departure, CapacityHold, Booking, Passenger and PaymentReceipt; active holds plus confirmed seats may never exceed capacity, and payment identity is deduplicated. - Project rule — scope and recovery: Payment integration needs current provider webhook rules and a refund policy. Do not treat browser redirects as proof of payment or electronic waiver capture as legal enforceability. - Project rule — acceptance: Two parties request the last two seats while a hold expires and payment arrives late; reconcile the payment without overselling and surface any required refund decision. - Project rule — delivery: document real setup commands and permissions; do not claim a build, accuracy level, performance result or security certification that has not been demonstrated. ## Optional agent skills and references - Recommended skill: [supabase-postgres-best-practices](https://github.com/supabase/agent-skills/blob/main/skills/supabase-postgres-best-practices/SKILL.md) — review this PostgreSQL domain schema, uniqueness constraints, transaction boundaries and access-scoped queries; Supabase hosting is not required. Follow the maintainer's installation instructions and match its requirements to the chosen runtime. - Recommended skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — review keyboard access, focus, validation, error recovery and the readable work/review interface or HTML report. Follow the maintainer's installation instructions and match its requirements to the chosen runtime. - Recommended skill: [stripe-best-practices](https://github.com/stripe/ai/blob/main/skills/stripe-best-practices/SKILL.md) — design the optional hosted checkout, verified webhook and entitlement/refund state transitions using the current Stripe integration guidance. Follow the maintainer's installation instructions and match its requirements to the chosen runtime. Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism. ## Distribution ideas These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone. - Demonstrate this working slice using synthetic or explicitly authorized non-sensitive examples: Define tour departures with seat capacity, hold seats during checkout and provide staff with a check-in manifest and explicit cancellation/refund states. - Share a synthetic example export and the acceptance walkthrough; keep real customer, health, financial and source data private: Two parties request the last two seats while a hold expires and payment arrives late; reconcile the payment without overselling and surface any required refund decision. - State the limits before asking someone to replace their existing tool: Payment integration needs current provider webhook rules and a refund policy. Do not treat browser redirects as proof of payment or electronic waiver capture as legal enforceability. ## Engineering roadmap 1. Phase 1 — Pin the working slice and create its example input: Define tour departures with seat capacity, hold seats during checkout and provide staff with a check-in manifest and explicit cancellation/refund states. Confirm setup: A PostgreSQL database, departure/capacity examples, the operator timezone, a Stripe sandbox account with webhook setup and an authenticated staff role. 2. Phase 2 — Implement persistence and write-time invariants before decorating the UI: Store Tour, Departure, CapacityHold, Booking, Passenger and PaymentReceipt; active holds plus confirmed seats may never exceed capacity, and payment identity is deduplicated. 3. Phase 3 — Connect the working view to real saved state. Use transactional capacity holds against dated departures, not personal calendar free/busy. Store verified payment events and reconcile late/failed payments; confirmation requires capacity and payment state to agree. 4. Phase 4 — Expose the app-specific limits and recovery path in context: Payment integration needs current provider webhook rules and a refund policy. Do not treat browser redirects as proof of payment or electronic waiver capture as legal enforceability. 5. Phase 5 — Walk through this concrete acceptance case and preserve its exported evidence: Two parties request the last two seats while a hold expires and payment arrives late; reconcile the payment without overselling and surface any required refund decision. Finish the README and backup/restore instructions; report unfinished capabilities explicitly. ## Paid-product capabilities outside this build - OTA and reseller distribution: live availability pushed to Viator, GetYourGuide, Expedia and dozens of local agents, plus the commission accounting behind it - Someone else owning payment risk: chargebacks, disputes, refund flows, payout timing, PCI scope and multi-currency - 24/7 human support during a season where a broken booking page costs real departures that day - The messy operational features you only miss in August: resource and guide assignment, gear allocation, multi-day and multi-activity itineraries, gift cards, promo codes, waivers, group and private bookings - Mobile check-in that works on a beach with one bar of signal, and the reporting your accountant already knows how to read ## Implementation prompt Build the following focused alternative to FareHarbor. This is a deliberately limited personal or small-team substitute, not parity with the paid service. WORKING SLICE Define tour departures with seat capacity, hold seats during checkout and provide staff with a check-in manifest and explicit cancellation/refund states. SETUP AND ARCHITECTURE Use TypeScript, React, Node, PostgreSQL and hosted Stripe Checkout for one tour operator. Prerequisites: A PostgreSQL database, departure/capacity examples, the operator timezone, a Stripe sandbox account with webhook setup and an authenticated staff role. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success. DOMAIN MODEL AND INVARIANTS Store Tour, Departure, CapacityHold, Booking, Passenger and PaymentReceipt; active holds plus confirmed seats may never exceed capacity, and payment identity is deduplicated. IMPLEMENTATION CONTRACT Use transactional capacity holds against dated departures, not personal calendar free/busy. Store verified payment events and reconcile late/failed payments; confirmation requires capacity and payment state to agree. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content. APP-SPECIFIC BOUNDARY AND RECOVERY Payment integration needs current provider webhook rules and a refund policy. Do not treat browser redirects as proof of payment or electronic waiver capture as legal enforceability. ACCEPTANCE SCENARIO Two parties request the last two seats while a hold expires and payment arrives late; reconcile the payment without overselling and surface any required refund decision. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested. DELIVERY Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product. PROJECT RULES FOR AGENTS.md Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication. ## Completion evidence Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.