What problem does it solve? Pointing a domain you already own at a Convex app involves multiple error-prone steps: creating the right DNS records at your registrar, attaching the custom domain to Convex, and rebinding your auth origin so sign-in keeps working. This Skill walks through the entire process and prevents common mistakes like missing TXT verification records or broken auth after the switch. ## Core Features & Use Cases - DNS Record Setup: Detects an already-authenticated DNS CLI (flarectl, aws, gcloud, doctl, vercel) and offers to create the CNAME/A and TXT verification records automatically, or gives exact record values for manual entry at your registrar. - Custom Domain Attachment: Attaches the domain as a Convex custom domain and verifies propagation with dig. - Auth Origin Rebinding: Updates SITE_URL, RP_ID, and ORIGIN environment variables so passkeys and OAuth keep working on the new domain. - Use Case: You deployed a booking app on Convex and want it served at bookings.example.com instead of the default convex.app URL, without breaking existing user sign-ins. ## Quick Start Point my domain example.com at my Convex app and update the auth settings so login still works.
