Youth Sports Team Messaging Hub

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "TeamComm": a coach posts one update and every parent who opted in gets it by text and email, with a one-word RSVP reply. It holds parents' contact details and a child's first name only, and parents opt in themselves.
   
   Stack: Next.js (App Router, TypeScript), Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link for coaches), Twilio Programmable Messaging for text, Resend for email. A parent joins through an invite link and ticks a consent box; there is no parent login. A Vercel Cron route sends reminders. Deploy on Vercel.
   
   Tables (Row Level Security on, a coach reads only their own team's rows; the join and the SMS webhook write through the service role):
   - teams(id, name, sport, coach_user_id, invite_code)
   - families(id, team_id, parent_name, phone, email, athlete_first_name, sms_opt_in_at, email_opt_in_at, opted_out_at)
   - events(id, team_id, type, starts_at, location) type is game, practice or other
   - messages(id, team_id, body, tag, created_at) tag is schedule, urgent, payment or general
   - deliveries(id, message_id, family_id, channel, status, delivered_at, provider_id)
   - rsvps(id, event_id, family_id, status)
   
   Screens: /login, /team (the roster and events), /post (write and send), /join/[inviteCode] (the parent's page), /messages/[id] (delivery status).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_PHONE_NUMBER, RESEND_API_KEY, CRON_SECRET.
   
   Do not build: billing or team plans, fees and payments, carpool, push notifications or a mobile app, a model for replies, importing phone numbers a parent did not enter.
   Done when: npm run dev starts, you can sign in, and the six tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves TeamComm: one post reaches every family on the channel they agreed to, and an urgent change never gets lost.
   1. A coach creates a team and shares its invite link. A parent opens it, enters their name, phone, email and the child's first name only, and ticks separate boxes for text and email with clear wording. Save the time of each consent. Never take a child's last name, age or photo.
   2. A coach can import a roster CSV of names and emails only. Those families get no text until they opt in through the link.
   3. The post page takes a message and a tag. Sending creates a delivery for each family on each channel they opted into: a text through Twilio and an email through Resend. Skip anyone who has opted out. Send urgent messages first.
   4. Twilio and Resend status webhooks update each delivery. /messages/[id] shows delivered and failed counts per family so the coach sees who was missed.
   5. POST /api/sms validates the Twilio signature and matches the sender to a family. A reply of YES or NO (any case, with or without a trailing word) sets the RSVP for the team's next event and replies "Got it". Anything else gets "Reply YES or NO, or STOP to end texts". STOP sets opted_out_at.
   6. A daily cron route (protected by CRON_SECRET) sends a reminder the day before each event to opted-in families.
   Rules: only text a number the parent entered themselves. Every text says who it is from and how to stop. Store every inbound and outbound message for the coach's record. Honor business-text registration rules by sending from a registered number only.
   Empty state: a new team shows the invite link and what parents will be asked.
   Done when: a parent can opt in for text only, a roster import sends nothing, a post reaches opted-in families on their channels, a YES reply sets the RSVP, STOP ends texts and a failed delivery shows against the right family.

3. 3. Landing Page

   Build a one-page landing site for TeamComm, team messaging for youth sports coaches and parents.
   Hero: "Every parent gets the update. Every time." Sub: "Post once. We send it by text and email to the parents who chose it, so nobody shows up to a moved game." One button: Join the waitlist.
   Sections: a coach posting a game-time change and three parent phones receiving it, the problem (updates scattered across group chats, email and league portals), how it works in four steps (invite parents, post once, parents reply YES or NO, see who got it) and an FAQ on business text registration, children's data (parents' contact details and a child's first name only) and no app for parents.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: Geist, an off-white background, near-black type, one lime accent, generous whitespace.
   Done when: the page renders on a phone and a submitted email appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for TeamComm: a wordmark and a small icon that suggest one chat bubble radiating outward.
   Colors: near-black, one lime and two warm neutrals. Type: Geist for the interface, Geist Mono for delivery timestamps.
   Deliverables: wordmark, icon, a six-icon set (post, schedule, RSVP, alert, text, email), three sample game-day texts under 160 characters, and a one-page brand sheet. Voice rules: lead with the parent's peace of mind, never blame the coach.
   Done when: each deliverable is saved in one folder and each sample text is under 160 characters.