メニュー
Use when drafting a technical orange-book, handbook, or long-form guide that must feel like a knowledgeable human wrote it from use and judgment, not like official docs paraphrased into prose.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when rendering a technical manuscript into a polished HTML and PDF orange-book with a custom cover, table of contents, book-like spacing, and printable A4 layout.
Use when writing a technical orange-book or handbook that should read like a product manual with explicit judgment, dense tables, and stable chapter structure rather than a polished blog post.
Use when turning research notes into a book structure, chapter tree, and writing plan for a technical guide, orange-book, or whitepaper.
Use when a long-form technical draft is factually decent but still feels generic, too smooth, or too AI-written and needs sharper voice, specificity, and pacing.
Use when preparing a technical book, orange-book, or long-form guide and the draft must be grounded in official documentation, release notes, and a saved evidence ledger before writing starts.
Use when a book project has multiple chapters or sections that can be researched, drafted, or revised in parallel by separate agents without sharing a write target.
| name | mj-book-writer |
| description | Use when drafting a technical orange-book, handbook, or long-form guide that must feel like a knowledgeable human wrote it from use and judgment, not like official docs paraphrased into prose. |
写技术橙皮书，不是把官方文档翻译成中文。
这份 skill 吸收了 makerjackie-writer 里最有效的部分，但把目标换成了技术书写作：要讲人话，要有作者判断，要知道读者卡在哪里，同时又不能牺牲事实密度。
每一章开写前，先写出 3 句内部草稿，不必出现在正文里：
没有这 3 句，正文很容易沦为文档改写。
技术书最容易写坏的地方，是第一段就变成“X 是一个……”。更好的顺序通常是：
每章至少回答下面四个问题中的三个：
理想节奏不是：
而是：
至少做到其中两个：
从一个真实使用入口切，不要从大词切。
好开头像这样：
坏开头像这样：
一章建议按下面的顺序推进：
结尾不要写成“综上所述”。更好的收法是：
写完每章，至少过这 6 条：
不要为了“全”把每个产品都写得一样重。读者真正需要的是：
永远分成三条线：
对于价格、限额、可用区域、产品支持范围这些容易变化的内容：
