Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 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-book-swarm |
| description | 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. |
把一本书拆成可以并行推进的写作单元。
mj-book-polish