القائمة
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.
التثبيت باستخدام 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 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.
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.
| name | mj-orange-book-writer |
| description | 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. |
这不是营销写作，也不是个人散文。
它的目标更接近 openclaw-orange-book：把复杂产品写成一套稳定的技术手册。读者翻开任意一章，都应该能迅速看到判断、表格、边界、建议，而不是先看三段铺垫。
核心建议 收口。如果一章只允许一张表，优先写下面这些：
每一章至少覆盖下面四项里的三项：
这本书真正要解决的不是“Cloudflare 有什么”，而是：
永远分成三条线：
价格、限额、地区支持范围都可能变化。写法优先级是：