Use Claude to build wedding RSVP and guest tools
Piotr Szaran built a wedding website for himself and his fiancée, designed for around two hundred guests. It needed to communicate event details, collect RSVPs and give the couple a practical way to manage responses and guest information.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a wedding site with public details, custom RSVPs, guest imports and an authenticated dashboard for us. Generate design options first, then implement the selected direction and review mobile guest flows.
Reach people exploring AI agents
See placements →What happened
Wedding information and custom RSVPs with an authenticated couple dashboard, guest imports and email broadcasting; no final response count reported.
Reported by Piotr SzaranHow the agent did it
- Define wedding information, RSVP and guest-management requirements.
- Generate design options and guide implementation in smaller tasks.
- Review mobile guest flows and monitor the live site's behavior.
Where a person stepped in
Szaran selected designs, reviewed revisions and checked guest, admin and mobile workflows.
Piotr Szaran built a wedding website for himself and his fiancée, designed for around two hundred guests. It needed to communicate event details, collect RSVPs and give the couple a practical way to manage responses and guest information.
He used Claude Code through a guided process, supplying context and breaking work into manageable tasks. Supporting instructions in skills.md helped shape the output. For design exploration, Claude and the frontend-design skill produced fifteen different directions; Szaran selected and combined elements rather than accepting a single generated design.
The resulting application included a custom RSVP flow, an authenticated dashboard for the couple, guest imports and email broadcasting. Supabase supported authentication and guest data. Mobile use shaped the layout and performance decisions because many guests would check information from phones.
Szaran reviewed generated work, revised the direction and examined guest and admin workflows. He added Sentry to observe issues after launch and describes additional attention to edge cases and reliability. He also says he would document the agent workflow more deliberately and tighten parts of the code after rapid iteration. The account reports a working event-management site, without supplying a final count of submitted RSVPs or measured time savings.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: www.piotrszaran.com · Piotr Szaran
Frequently asked questions
Why include an authenticated dashboard?
The couple needed to manage guest information and track responses behind the public wedding page.
Who chose the design?
Claude generated fifteen directions; Szaran curated and combined the pieces he preferred.
What made mobile behavior a priority?
The expected audience included family and friends checking details and responding from their phones.
More details
About this account
Claude generated design directions and implemented RSVP, dashboard and guest-management features.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Piotr Szaran
Source published 17 Mar 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Supabase · Sentry · frontend-design skill
Wedding RSVPs · Guest management · Family event
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.