| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.5 KB |
| references/durable-context.md | markdown | 2.0 KB |
| references/mode-long-form.md | markdown | 2.5 KB |
| references/mode-public-reply.md | markdown | 4.3 KB |
| references/mode-release-notes.md | markdown | 4.4 KB |
| references/mode-revision-review.md | markdown | 3.2 KB |
| references/write-en.md | markdown | 9.3 KB |
| references/write-product-localization.md | markdown | 12.9 KB |
| references/write-technical.md | markdown | 8.5 KB |
| references/write-zh-bilingual.md | markdown | 1.5 KB |
| references/write-zh-release-notes.md | markdown | 2.2 KB |
| references/write-zh.md | markdown | 53.3 KB |
| scripts/check-punctuation.sh | script | 151 B |
| scripts/check_punctuation.py | script | 18.9 KB |
references/write-zh-release-notes.md
View on GitHub# 对外发文专项:release notes 和推文
## 推文 / 社交发文五规则
适用于已有社区语气和轻量发布节奏的产品工程师项目对外发文:
1. **社区先行**:开头用社会锚点(star 数、感谢用户、谁的反馈推动了这次修复)。改动清单跟在后面,不放在最前。
2. **亮点不全量**:挑 2 到 4 个最有意思的改动。跳过整个模块也没问题。读者要的是故事,不是 changelog。
3. **用户感受帧**:每条写法用"你用它的时候…"或"有一种…的感觉",不是"这个工具做了…"。
4. **一条立场**:至少一句表明决策原因的意见句(例:"我更相信模型本身的能力,而非各种规则限制他的天花板")。
5. **中文节奏**:用地道表达(给留了一手、玩玩、大伙、大概就是这些)。避免翻译腔和正式词(具体判据、主轴、本意)。
结尾用邀请,不用 CTA:「假如没有用过的小伙伴,欢迎去试试看,玩玩。」而不是「立即升级」。
## Release Notes 格式
**结构**:Breaking Changes → New Features → Fixes & Improvements → Deprecations
**格式**:优先匹配目标项目最近一次 release。没有可用参考时,使用编号列表、bold 标签、一句话说用户效果;只有目标项目已经使用中英双语时才输出双语,中英版本条目数一一对应。
**长度参考**:沿用上一个版本的格式、句子长度和信息密度,不把条目数当配额。本次有几个独立的用户结果就写几条,完整说清后立刻停。
**边界**:GitHub Release 正文和社交公告是两份 artifact。Release notes 解释用户会感受到什么,默认不写 CI、tap、registry、API 名称、fallback 路径等机制细节;公告另按社交发文规则挑 2 到 4 个亮点。
## 对外发文专项检查
脱敏、不踩竞品、用户感受先于功能清单这三件事见 `write-zh.md` 的「对外发文专项检查」,交稿前按那里扫一遍。
## 发版前检查
- 不出现"不再更新"、"final release"、"停止维护"等终止信号(除非是真实情况)
- release title 简洁:版本号 + 最核心的改动或主题,不超过 10 个词
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| algorithmic-artanthropics/skillsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-gainDietrichGebert/ponytailShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact". | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-reviewDietrichGebert/ponytailQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |