← ClaudeAtlas

supabase-auth-emailslisted

Replace Supabase Auth's default emails (confirmation, magic link, recovery, invite, email change) with branded React Email templates, wire them through supabase/config.toml, push them to the hosted project with supabase config push, and prove they render and deliver. Use this whenever the work touches Supabase auth emails or templates, [auth.email.template.*] or content_path in config.toml, {{ .ConfirmationURL }} or {{ .TokenHash }}, React Email rendered to static HTML for Supabase, custom SMTP via [auth.email.smtp] or Resend, Mailpit or Inbucket on localhost:54324, magic links that fail on another device, "Email link is invalid or has expired", "both auth code and code verifier should be non-empty", or auth emails that never arrive, land in spam, or still look like the Supabase default in production. Reach for it even for "just restyle the confirmation email", because the failures here are silent and reach customers. Not for product emails sent from application code, and not for the auth routes themselves.
tanfust/skills · ★ 0 · API & Backend · score 73
Install: claude install-skill tanfust/skills
# Supabase Auth emails with React Email Two things go wrong with auth emails, and neither throws. The template looks right in the local mail catcher and production keeps sending the Supabase default, because `config.toml` is local configuration and nobody pushed it. Or the email arrives, the button works on the laptop that requested it, and fails for every customer who opens it on their phone, because the link depends on a cookie that only exists in the first browser. So the work is not finished when the template renders. It is finished when a link from a real send, opened in a browser that did not request it, produces a signed-in session, locally and on the hosted project. This skill covers the five action emails Supabase lets you template: `confirmation`, `magic_link`, `recovery`, `invite`, `email_change`. React Email is the authoring tool; Supabase only ever sees static HTML with Go template variables in it. ## Order of work 1. Decide the link flow before writing any template 2. Set up custom SMTP, because the default sender does not reach customers 3. Write the templates against a shared layout 4. Build to static HTML with the Go variables passed through as props 5. Wire `config.toml` and restart the local stack 6. Push to the hosted project 7. Verify: build, send, open on another device, check production ## 1. Decide the link flow `{{ .ConfirmationURL }}` points at Supabase's `/auth/v1/verify` endpoint, which verifies the token and redirects to your site. With the