email-and-notifications
Skill10 starsChanged 6 months agoMITView on GitHub
Use when sending transactional email (Resend, Postmark, etc.), magic links, notification templates, or email edge functions. Not for in-app toast-only UX or SMS unless extending the same pattern.
- Reads credentials
- Sends data out
In this repository56 other files it gives its agents.
- accessibility-passSkill
- analytics-eventsSkill
- api-error-handlingSkill
- audit-logging-backendSkill
- background-jobs-and-cronSkill
- dark-mode-and-themingSkill
- dashboard-charts-rechartsSkill
- edge-functions-and-webhooksSkill
- error-states-and-empty-uiSkill
- feature-flags-and-togglesSkill
- file-upload-storageSkill
- i18n-multi-languageSkill
- lovable-prompting-playbookSkill
- lovable-ship-checklistSkill
- migration-playbookSkill
- multi-tenant-backendSkill
- onboarding-copySkill
- optimistic-updatesSkill
- payment-failed-and-recoverySkill
- payment-webhook-idempotencySkill
- payment-webhook-testingSkill
- performance-budgetSkill
- pg-cron-recipesSkill
- pg-cron-scheduled-jobsSkill
- pg-cron-with-pg-net-edgeSkill
- postgres-full-text-searchSkill
- postgres-triggers-and-functionsSkill
- pricing-and-billingSkill
- programmatic-seo-content-qualitySkill
- programmatic-seo-pagesSkill
- rate-limiting-edgeSkill
- realtime-and-subscriptionsSkill
- refactor-safe-diffSkill
- release-notesSkill
- seo-core-web-vitalsSkill
- seo-landing-pageSkill
- seo-meta-tags-spaSkill
- seo-sitemap-generationSkill
- seo-ssr-and-prerenderingSkill
- seo-structured-dataSkill
- server-input-validationSkill
- shadcn-patternsSkill
- soft-delete-and-archivingSkill
- stripe-one-time-payment-webhooksSkill
- stripe-payment-webhooksSkill
- supabase-auth-flowsSkill
- supabase-database-designSkill
- supabase-rls-and-authSkill
- support-replySkill
- tanstack-infinite-queriesSkill
- tanstack-mutations-and-invalidationSkill
- tanstack-prefetch-and-hydrationSkill
- tanstack-query-alternativeSkill
- tanstack-router-data-loadersSkill
- tanstack-start-server-routesSkill
- typed-api-hooks-formsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Test in Gmail, Outlook, and a mobile client at least once before launch.
- Distinctive: line 51
Avoid spam triggers in subject lines (ALL CAPS, "FREE!!!", excessive emojis).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Email and notifications
Send email from edge functions with API keys in Supabase secrets — never in the client.
Transactional email
- Templates: welcome, password reset (prefer Supabase Auth built-in), receipt, invite.
- Idempotent sends: store
email_log(id, template, user_id, sent_at)to prevent duplicates on retry. - From address on verified domain.
Edge function sketch
const res = await fetch("https://api.resend.com/emails", {
method: "POST",
headers: {
Authorization: `Bearer ${Deno.env.get("RESEND_API_KEY")}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ from, to, subject, html }),
});Validate caller: webhook, cron, or authenticated invoke with JWT check.
In-app notifications
- Table:
notifications(user_id, title, body, read_at, created_at). - RLS: user reads own rows only.
- Realtime optional (
realtime-and-subscriptionsskill). - Bell icon + unread count; mark read on open.
Templates and rendering
- Build emails with react-email (
@react-email/components) and render to HTML in the edge function — gives you typed, previewable templates. - Include a plain-text fallback (
textfield on Resend / Postmark). - Test in Gmail, Outlook, and a mobile client at least once before launch.
Deliverability basics
- SPF, DKIM, and DMARC configured for the sending domain (provider docs).
- From address on a verified domain (
hello@yourdomain.com), notgmail.com. - Avoid spam triggers in subject lines (ALL CAPS, "FREE!!!", excessive emojis).
Avoid
- API keys in
VITE_*. - Sending email synchronously in the client on button click without a server.
- PII in log lines.
- Single template that branches on 10 product flows — split per template.
Checklist
- Secrets in edge env only.
- Unsubscribe / legal footer on marketing email.
- Idempotent on retry (
email_logkeyed by event id). - Deliverability records (SPF/DKIM/DMARC) configured.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

