跳到主内容
@wquguru
精选86VoxAI 产品与模型

Claude Code技巧:用Opus 5.5审查邮件发送配置

Claude Code tip: if your vibe-coded app sends any email, have Opus 5.5 send out…

原文
发到 X
推荐理由

提供了极具实操价值的 AI 工作流设计,展示了如何将复杂的工程检查拆解为多 Agent 协作,且 Prompt 细节丰富可直接复用。

Claude Code tip: if your vibe-coded app sends any email, have Opus 5.5 send out 𝟰 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 before you ship to check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟱 𝘁𝗵𝗶𝗻𝗴𝘀, then fix them all in one pass:

Claude Code 技巧:如果你的 vibe-coded 应用会发送任何邮件,在发布前让 Opus 5.5 派出 𝟰 个 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 来检查这 𝟭𝟱 件事,然后一次性修复所有问题:

Sending setup → Still sending sign-up codes and password resets through Supabase's built-in email? It only delivers to your team members, 2 messages an hour. Switch to a sending service on your own domain → Send from your own domain, not a free Gmail address, and set Reply-To to an inbox someone actually reads → Set up SPF, DKIM and DMARC, aligned with your sending domain → Send marketing email and notifications like sign-up codes from different addresses or subdomains, so complaints about marketing drag down your codes less

发送设置 → 还在通过 Supabase 内置的电子邮件发送注册验证码和密码重置邮件吗?它只能发送给团队成员,每小时仅 2 封。切换到你自己域名的发送服务 → 从你自己的域名发送邮件,而不是免费的 Gmail 地址,并将 Reply-To(回复至)设置为有人实际阅读的收件箱 → 设置 SPF、DKIM 和 DMARC,并与你的发送域名对齐 → 从不同的地址或子域名发送营销邮件和通知(如注册验证码),这样针对营销邮件的投诉对验证码送达率的影响较小

Login and codes → Opening a login, verification or reset link shouldn't use it up. Make the user click a button on the page, or just send a 6-digit code. Company mail scanners click the link before the user does → Hook up your sending service's bounce and complaint webhooks: stop sending to hard bounces and complaints, stop after repeated soft bounces too, and don't resend codes that have already expired

登录与验证码 → 打开登录、验证或重置链接不应消耗配额。让用户点击页面上的按钮,或者直接发送 6 位验证码。公司邮件扫描仪会在用户之前点击链接 → 接入你发送服务的退信和投诉 Webhook:停止向硬退信和投诉地址发送,重复软退信后也停止发送,并且不要重新发送已过期的验证码

Bulk mail and unsubscribes → Put one-click unsubscribe (List-Unsubscribe and List-Unsubscribe-Post) on marketing email and honor it within 2 days. It's mandatory if you send Gmail more than 5,000 a day → Ramp up a new domain on a schedule. Don't blast your whole list on day one → Block disposable addresses, typo'd domains (gmial instead of gmail) and domains with no MX record before they reach your list → Watch your complaint rate in Gmail's Postmaster Tools. Keep it under 0.1%. Around 0.3%, your mail is likely to get rejected → Apple Mail loads images automatically, which inflates opens. Company security scanners click links automatically, which inflates clicks. Take both out of your stats

批量邮件与退订 → 在营销邮件上添加一键退订(List-Unsubscribe 和 List-Unsubscribe-Post),并在 2 天内予以尊重。如果你每天发送超过 5,000 封 Gmail 邮件,这是强制要求的 → 按计划逐步提升新域名的信誉度。不要在第一天就向整个列表群发 → 在邮件进入你的列表之前,屏蔽临时邮箱地址、拼写错误的域名(如 gmial 而非 gmail)以及没有 MX 记录的域名 → 关注 Gmail Postmaster Tools 中的投诉率。保持在 0.1% 以下。如果达到约 0.3%,你的邮件很可能被拒收 → Apple Mail 会自动加载图片,这会虚高打开率。公司安全扫描仪会自动点击链接,这会虚高点击率。将这两者从统计数据中剔除

The email itself → Build the HTML with tables and inline styles so it holds up in Outlook → Keep the HTML code under 102KB (images don't count). Over that, Gmail clips the rest, and the unsubscribe link at the bottom disappears with it → Include a plain-text version with every email → Preview variables like first name with a fake subscriber, so you never send "Hi {first_name}"

邮件本身 → 使用表格和内联样式构建 HTML,以确保其在 Outlook 中正常显示 → 保持 HTML 代码在 102KB 以内(图片不计入)。超过此限制,Gmail 会截断剩余内容,底部的退订链接也会随之消失 → 每封邮件都包含纯文本版本 → 使用假订阅者预览变量(如名字),确保永远不会发送 "Hi {first_name}"

The default medium effort is enough. The login and codes group has to read your sending and webhook code, so raise that one to high.

默认的中等工作量已足够。登录和验证码组需要阅读你的发送和 webhook 代码,因此将该组的工作量提升至高。

Send this whole post to Claude Code. If you need to, add this line at the end 👇 "Send one subagent per group to check it without editing anything, and note which file or dashboard each issue is in. Run the login and codes subagent at high effort. For the email service key, report only where it is and never paste its value. Only send test emails to my own test inbox, and don't call any bulk-send endpoint. Send one email to my Gmail, and I'll paste you the SPF, DKIM and DMARC lines from 'Show original'. For DNS, Postmaster Tools and the sending service's dashboard, give me the steps and I'll do them myself. Show me the list of issues first, don't change anything until I confirm, and when you're done, give me a pass/fail table."

将此完整帖子发送给 Claude Code。如有需要,在末尾添加以下行 👇 “每个组发送一个子代理进行检查,不编辑任何内容,并注明每个问题所在的文件或仪表板。以高努力程度运行登录和代码子代理。对于电子邮件服务密钥,仅报告其位置,切勿粘贴其值。仅向我的测试收件箱发送测试邮件,不要调用任何批量发送端点。向我自己的 Gmail 发送一封邮件,我将把‘显示原始内容’中的 SPF、DKIM 和 DMARC 行粘贴给你。对于 DNS、Postmaster Tools 和发送服务的仪表板,请提供步骤,由我自己操作。先列出问题清单,在我确认之前不要更改任何内容,完成后,提供一个通过/失败表格。”

更进一步:量化金融体系

看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力

进入量化体系 →

相似阅读

关联信息,但可能不是同一事件