菜单
Write release notes, what's new posts, and ship announcements that tell users what shipped in their terms. Use whenever the user mentions release notes, changelog, what's new, ship announcement, version notes, or needs to communicate what changed in a release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit a brand's full identity (logo, typography, color, voice, visual language) for consistency, distinctiveness, and gap. Use when the user asks for a brand audit, identity review, brand health check, or wants to evaluate how a brand shows up across surfaces.
Plan a content calendar tied to product, brand, or marketing goals. Use when the user asks for a content plan, editorial calendar, content strategy, posting schedule, or wants to map content to themes and audiences over a period of time.
Write a sequence of emails for onboarding, nurture, sales, lifecycle, or launch. Use when the user asks for a drip campaign, email sequence, welcome series, onboarding emails, sales cadence, or any multi-email flow tied to a goal.
Design an a/b test or experiment including hypothesis, metrics, sample size, and analysis plan. Use whenever the user mentions a/b test, experiment, split test, multivariate test, or needs to design a test that produces a decision-quality result.
Audit a design or component for WCAG accessibility compliance. Use whenever the user mentions a11y, accessibility audit, WCAG check, contrast issues, keyboard navigation, screen reader support, focus order, or asks if a design is accessible.
Extract a brand voice guide from existing copy samples. Use whenever the user shares past copy and asks to define a voice, document a voice, create voice guidelines, or wants to make their existing voice teachable and repeatable.
| name | release-narrative |
| description | Write release notes, what's new posts, and ship announcements that tell users what shipped in their terms. Use whenever the user mentions release notes, changelog, what's new, ship announcement, version notes, or needs to communicate what changed in a release. |
release notes are user-facing. they exist to help users get value from what shipped. write for them, not for the internal team.
[version] — [date]
[one-sentence summary of the headline change in user value terms]
new
- [feature]: [what it does for the user, in their language]
improved
- [improvement]: [the before and after, concretely]
fixed
- [bug]: [the symptom, not the technical cause]
breaking changes (only when present)
- [thing]: [old behavior → new behavior, with migration step]
heads up (only when present)
- [anything that affects workflow even if not a breaking change]
the most important change to the most users goes first. internal ordering, alphabetical ordering, or ticket-number ordering all serve the team, not the reader.
if you need two sentences, the item is two items, or you're explaining instead of stating.
what the user sees and does. not what the database does.
usually past tense for what shipped. don't mix "added" and "you can now".
no jira ticket numbers in user-facing notes. no internal project codenames. no "as discussed in the #product channel".
if there's a breaking change, label it clearly, name the old and new behavior, and tell users exactly what to change.
calm. confident. specific. write like a colleague telling another colleague what happened, not like a marketing department.
if the brand voice is more playful, the structure stays the same; the diction relaxes a notch. don't sacrifice clarity for personality.
[version] — [date]
[summary sentence]
new
- [items in user-impact order]
improved
- [items in user-impact order]
fixed
- [items in user-impact order]
breaking changes (if any)
- [items with migration steps]
heads up (if any)
- [items]
length depends on the release. a small patch may be three bullets. a major release with breaking changes may be a longer post with deep-link sections.