菜单
Designs email sequences that onboard, educate, and retain users — welcome series, drip campaigns, and re-engagement. Use when sign-ups don't activate, users go quiet, or you need automated nurture beyond social posts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.
Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.
Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."
Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.
Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.
Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.
基于 SOC 职业分类
| name | email-nurture |
| description | Designs email sequences that onboard, educate, and retain users — welcome series, drip campaigns, and re-engagement. Use when sign-ups don't activate, users go quiet, or you need automated nurture beyond social posts. |
Social gets attention; email owns the relationship. For developer products, email works when it teaches something useful — not when it spams "Come back!" every day.
Chains from [[growth-strategy]] (ICP, activation metric) and [[content-marketing]] (repurpose articles). Complements [[community-engagement]] (event invites) and [[referral-loop]] (referral asks in sequence).
Use email-nurture checklist alongside this process.
Skip when: no email collection, no product to link to, or list is bought/scraped (never).
| Sequence | Trigger | Goal |
|---|---|---|
| Welcome | Sign-up | First action in 24h |
| Activation | No first action by Day 1 | Complete profile / first connection |
| Onboarding | Day 1–7 | Habit + value discovery |
| Re-engagement | Inactive 14+ days | Return visit |
| Newsletter | Opt-in engaged users | Trust + updates |
One primary goal per email — not five CTAs.
| Day | Subject angle | CTA |
|---|---|---|
| 0 | Welcome + one quick win | Complete profile |
| 1 | How others use it (story) | First connection |
| 3 | Tip / tutorial snippet | Try feature |
| 7 | Community / showcase | Join discussion |
| 14 | Feedback ask | Reply or survey |
Draft full copy: subject (≤50 chars), preview text, body (scannable), single CTA button.
| Metric | Target (industry rough) |
|---|---|
| Open rate | 35%+ (dev lists) |
| Click rate | 3%+ |
| Unsubscribe | <0.5% per send |
| Activation lift | vs no-email cohort |
A/B test subject lines only after 500+ sends per variant.
