prose-writing

仓库创建 2026年6月4日最近提交 2 小时前SkillHot 收录 1 小时前

▸ 精选理由

确保所有用户面文案统一风格，适合产品、营销与文档团队使用。

这个 Skill 做什么

在撰写或编辑对外文案前提供统一的风格与语气指导校验。

在写对外文案、PR 评论、文档或 release notes 前，给出统一的风格和语气校验，确保所有面向用户的文字一致且合规。适用于任何 GitHub 可见文本、文档、博客、README 等需要对外展示的内容，写前先按这套规则过一遍。特别强调把 PROSE.md 作为单一事实来源，避免各处瞎改风格造成不一致。

▸ 展开 SKILL.md 英文原文

Copywriting / prose / tone style guide for EVERY user-facing or public-facing text artifact. INVOKE THIS SKILL (via the Skill tool) BEFORE writing or editing any of the following — and if you are a SUB-AGENT instructed to do any of them, invoke it yourself first; the agent that writes the copy loads this skill, the orchestrator does not load it on a sub-agent's behalf: (1) ANY GitHub-facing text — before `gh issue comment`, `gh pr comment`, `gh pr create` / any `--body`, `gh issue close --comment`, `gh pr review`, or `gh release create` / `gh release edit --notes`. (2) ANY documentation — `site/content/docs/**`, `site/content/blog/**`, `README.md`, `CHANGELOG`, `wiki/**` user-facing pages, or any `.md`/`.mdx` that ships to users. (3) Marketing / homepage / blog copy, a `package.json` or npm `description`, or any other description/summary field. (4) Whenever you APPLY a general copy-style correction — sweep it everywhere it applies, not just the one spot it was raised, and record it in

内容创作文案规范语气指南风格一致通用

3.9k

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/prose-writing/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/prose-writing/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# prose-writing

**The canonical guide is [`PROSE.md`](../../../PROSE.md) at the repo root — read it.** This skill exists to surface that guide whenever copy is being written, and to index it. PROSE.md is the single source of truth: do not duplicate its content elsewhere, and when a general copy rule is added or corrected, update PROSE.md and sweep every doc/page it applies to.

## When this applies

Any user-facing text: a GitHub issue/PR comment, a docs page, blog/marketing/homepage copy, release notes, a package/PR description field, or a chat reply. Also whenever you receive a *general* copy-style correction — apply it everywhere it's relevant, not only where it was raised.

**The agent

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有