メニュー
Use when sending product email — wire up Resend (or Postmark/SES) with typed React Email templates, send from background jobs not the request path, and cover deliverability basics like SPF/DKIM and unsubscribe.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when building API endpoints or server actions — validate every input with zod, return consistent typed JSON errors, set correct status codes, and authenticate/authorize before touching data.
Use when adding sign-in/sign-up or session handling to a SaaS app — set up Auth.js (NextAuth) or a hosted provider with secure sessions, OAuth + email, and server-side session checks that protect routes and actions.
Use when controlling what a user may do — implement role-based access control with a central permission map, server-side checks on every mutation, and a typed `can()` helper instead of scattered role string comparisons.
Use when work shouldn't run in the request path — offload emails, webhooks, exports, and scheduled tasks to a queue or job runner with retries, idempotency, and dead-letter handling instead of blocking the user.
Use when querying or mutating the database from the app — wrap Drizzle in server-only, tenant-scoped functions instead of calling the ORM from components, so every read/write is typed, testable, and isolation-safe.
Use when designing the Postgres schema or setting up Drizzle ORM — model users, organizations, memberships, and tenant-scoped tables with the right keys, indexes, timestamps, and migrations from day one.
| name | transactional-email |
| description | Use when sending product email — wire up Resend (or Postmark/SES) with typed React Email templates, send from background jobs not the request path, and cover deliverability basics like SPF/DKIM and unsubscribe. |
SaaS apps send email constantly: verification, invites, receipts, password resets, alerts. Use a provider built for it (Resend, Postmark, or SES) with React Email for typed, previewable templates. Treat sending as a side effect: trigger it from a background job, not inline in the request, so a slow mail API never blocks the user or fails their action.
// src/server/email/templates/Invite.tsx
import { Button, Html, Text } from "@react-email/components";
export function InviteEmail({ org, url }: { org: string; url: string }) {
return (
<Html>
<Text>You've been invited to join {org}.</Text>
<Button href={url}>Accept invite</Button>
</Html>
);
}
// src/server/email/send.ts
import "server-only";
import { Resend } from "resend";
import { env } from "@/env";
import { InviteEmail } from "./templates/Invite";
const resend = new Resend(env.RESEND_API_KEY);
export async function sendInvite(to: string, org: string, url: string) {
const { error } = await resend.emails.send({
from: "Acme <noreply@acme.com>",
to,
subject: `Join ${org} on Acme`,
react: InviteEmail({ org, url }),
});
if (error) throw new Error(`Email failed: ${error.message}`);
}
Call sendInvite from a job/queue (see background-jobs), and the action just enqueues it.
noreply@yourapp.com), not a free inbox.Reliable, typed email behind a service. background-jobs runs the actual send off the request path; observability-and-errors tracks failures.