菜单
Wire up transactional email for any app using Resend, Postmark, useSend, or Plunk. Sets up templates for welcome, password reset, notifications, and digests. Handles domain verification, deliverability, and unsubscribe. Use when the app needs to send emails to users.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Harden a self-hosted Linux server. Detects current state, runs a full interview to understand what the user wants, warns about edge cases (no SSH keys, password-only auth, provider firewalls), then implements only the selected steps in a safe order.
Systematic edge case discovery, test coverage, and hardening for any feature or codebase area. Spawns parallel subagents to enumerate edge cases across eight categories, writes tests for each, runs them, and fixes unhandled cases. Use after implementation to ensure robustness before shipping.
Add a time-boxed free trial to any app with a payment integration. Handles trial start, expiry tracking, gating, expiry emails, and the upgrade prompt flow. Use when adding a trial period to an existing subscription or paywall.
Convert any YouTube video into a reusable Claude Code skill. Paste a YouTube URL and this skill fetches the transcript, extracts the actionable content, and writes a ready-to-use .claude/skills/<name>.md file. Best for tutorial videos, how-to guides, workflow demos, or instructional content.
Make a site agent-ready using Cloudflare AI Search and the isitagentready.com checklist. Audits the current site, then implements: Cloudflare AI Search (hybrid vector + keyword), markdown content negotiation (acceptmarkdown.com), robots.txt AI rules, sitemap, MCP Server Card, and Agent Skills discovery. Use when asked to add search, make a site agent-ready, or optimize for AI agents.
Scaffolds a Better T Stack project via a structured interview. Uses AskUserQuestion to let the user pick frontend, backend, runtime, database, ORM, API layer, auth, payments, addons, example templates, and where to create the project. Assembles and runs the exact create-better-t-stack CLI command with no manual prompts.
| name | email-transactional |
| description | Wire up transactional email for any app using Resend, Postmark, useSend, or Plunk. Sets up templates for welcome, password reset, notifications, and digests. Handles domain verification, deliverability, and unsubscribe. Use when the app needs to send emails to users. |
You are wiring up transactional email end-to-end. Work through each phase in order.
Email types: {{args}}
Ask the user (combine related questions):
Spawn 2 parallel subagents:
| Subagent | Focus |
|---|---|
| 1 | Auth flows (signup, password reset), notification trigger points in the codebase |
| 2 | Existing email code, env vars, any current email setup |
Detect the package manager once (used by every provider below):
command -v bun >/dev/null 2>&1 && PM=bun || (command -v pnpm >/dev/null 2>&1 && PM=pnpm || PM=npm)
# Install CLI
irm https://resend.com/install.ps1 | iex # Windows
curl -fsSL https://resend.com/install.sh | bash # macOS/Linux
# Authenticate
resend login
# Create and verify sending domain
resend domains create --name mail.yourdomain.com --region us-east-1
resend domains list # get the domain ID
resend domains verify <id>
# Create an API key and copy it to .env
resend api-keys create --name "Production" --permission full_access
Install SDK: $PM add resend
Set RESEND_API_KEY in env vars.
Install SDK: $PM add postmark
POSTMARK_API_KEY (Server API token) in env varsDeploy via Docker or Railway (one-click): see https://docs.usesend.com
# After deploy, configure AWS SES credentials in the useSend dashboard
# Domain setup and DKIM/SPF are managed through the dashboard
Install SDK: $PM add usesend-js
Set USESEND_API_KEY and USESEND_BASE_URL in env vars.
# Deploy via Docker
docker pull useplunk/plunk
# Follow https://docs.useplunk.com for full self-hosting setup
Install SDK: $PM add @plunk/node
Set PLUNK_SECRET_KEY and PLUNK_BASE_URL in env vars.
Guide the user to add these DNS records for the sending domain:
v=spf1 include:<provider-include> ~allv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comUse React Email (default) for HTML templates:
$PM add @react-email/components react-email
Create emails/ directory with one file per template. Each template:
<Html>, <Head>, <Body>, <Container> from @react-email/componentsCreate a shared sendEmail(to, template, data) utility that:
For each email type, create a typed wrapper:
sendWelcomeEmail(user: { email, name })
sendPasswordResetEmail(user: { email }, resetUrl: string)
sendNotificationEmail(user: { email }, notification: Notification)
Wire each wrapper to the correct trigger point in the codebase.
mail.yourdomain.com) not the root domain"App Name <hello@mail.yourdomain.com>"