Menu
公众号全文生成。按确认的大纲和风格规范逐节撰写文章。
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | article-writer |
| description | 公众号全文生成。按确认的大纲和风格规范逐节撰写文章。 |
按照用户确认的大纲，依据行文风格规范逐节撰写公众号文章。
knowledge/style-guide.md 和 knowledge/glossary.mddocs/wechat/YYYY-MM-DD-<topic>-draft.md遇到专业术语
↓
查询 knowledge/glossary.md
↓
┌── 术语表中有 → 使用内置通俗解释
└── 术语表中无 → 联网搜索获取定义
↓
联网验证术语最新状态（工具是否更名/下线/更新）
↓
┌── 信息一致 → 直接使用
└── 信息不一致 → 以最新信息为准，并更新术语表
↓
首次出现：术语名（通俗解释）
后续出现：直接使用术语名
输出为Markdown格式的完整文章，保留以下标记供后续排版阶段使用：
**加粗文本**：核心结论==高亮文本==：关键数据/概念（排版时转为标蓝）<!-- 配图：描述 -->：配图占位标记> 引用文本：金句或引用---：视觉分隔线初稿完成后，自动进入自检优化（self-check）。
Posts content to WeChat Official Account (微信公众号) via API or Chrome CDP. Supports article posting (文章) with HTML, markdown, or plain text input, and image-text posting (贴图, formerly 图文) with multiple images. Markdown article workflows default to converting ordinary external links into bottom citations for WeChat-friendly output. Use when user mentions "发布公众号", "post to wechat", "微信公众号", or "贴图/图文/文章".
Complete document writing workflow: reference materials → brainstorming → planning → execution → review. Use when user wants to write articles, blog posts, technical docs, or any long-form content.
You MUST use this before any writing work - creating blog posts, technical documentation, reports, or any content. Explores topic intent, audience, and purpose before writing.
Reads and extracts context from reference materials (txt, markdown, pdf, images) placed in docs/reference/. Use at the start of any writing project to ground content in existing materials.
Use after article plan is approved. Searches and organizes reference materials (articles, images) for each section before writing begins. Invoked between planning and execution stages.
Enhancement plugin for generating high-quality code blocks in technical documentation. Ensures code examples are properly formatted, syntactically correct, runnable, and progressively complex. Invoked automatically by tech-doc-writing during execution stage.