Build your own Luma.

# Build an original app inspired by Luma

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original community-event platform called Gatherlist, inspired by Luma’s event and calendar workflow. Organizers publish a small event, guests request or confirm an RSVP, and hosts check in attendees. Start with free events, a limited organizer group, and a clear capacity/waitlist policy.

## Design
Create original event pages with a prominent title, date/timezone, location or online-link policy, host information, and RSVP state. Provide an organizer calendar, attendee list, and phone-friendly check-in screen. Make privacy and approval requirements visible before guests register.

## Features
1. Events and calendars: create draft/published/cancelled events, manage host-owned calendars, upload original cover images, and set start/end, IANA timezone, capacity, and RSVP deadline.

2. Registration: collect only necessary attendee fields, support approval-required or instant registration, prevent duplicate RSVPs, and allocate seats transactionally. Put excess eligible guests on a deterministic waitlist.

3. Guest management: approve, decline, cancel, and promote from the waitlist without exceeding capacity. Restrict attendee contact details and online joining links to the right roles.

4. Invitations and reminders: create explicit invitation links and calendar-file downloads with correct timezone data. Configure actual email delivery or show that messages are unsent; record delivery attempts for retry.

5. Check-in: issue unguessable QR check-in tokens, let authorized hosts scan or manually mark attendance, reject invalid/cancelled registrations, and make repeated scans idempotent.

## Tech stack
Use a TypeScript full-stack app, PostgreSQL, private organizer sessions, and a background reminder worker. Use a current IANA timezone library for scheduling and a maintained iCalendar serializer. Generate opaque QR tokens rather than embedding attendee email addresses.

## Data & behavior
User; Calendar; CalendarRole; Event {state, startsAt, endsAt, timezone, capacity}; Registration {guestId, status, waitlistPosition}; Invitation; CheckInToken {hash}; CheckIn; ReminderJob; DeliveryAttempt. Keep registration transitions and seat allocation atomic.

Acceptance checks and scope:
Test two simultaneous RSVPs for one seat, approval and waitlist promotion, guest cancellation, a daylight-saving event, repeated QR scans, unauthorized guest-list access, and a cancelled event reminder. Exclude paid tickets, refunds, video hosting, broad event scraping, and venue-booking integrations.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.