How to use Claude to finish a paid message board

A paid message-board creator described taking over a half-finished project after the original development team stopped delivering the work. They had spent substantial time troubleshooting and decided to take full responsibility. Claude Code helped them finish the site, but the author says roughly half their building time went into performance optimisation, security hardening, and alignment with European and Californian privacy standards.

The finished payment flow handles competing submissions with optimistic locking and automatic refunds. At payment initiation, the current post version is stored in Stripe PaymentIntent metadata. When the successful-payment webhook arrives, an atomic PostgreSQL update checks that version before activating the replacement. If another submission has already won, the payment is refunded and a WebSocket notification explains what happened.

The account also describes a per-user Redis lock to prevent double submissions and an idempotent activation path for Stripe webhook retries. These are reported implementation details, rather than evidence of independent security or compliance certification. The author separately drafts technical and promotional writing with LLMs, then edits and fact-checks it where relevant. Who it's for: developers inheriting unfinished applications who can devote attention to payments, concurrency, and operational behavior alongside agent-assisted coding.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Hacker News · SayThatSh