القائمة
Use when writing Manning-style technical chapters, Chapter 1s, examples, callouts, or summaries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when copy editing, proofreading, polishing, or removing AI-sounding prose.
Use when creating Data/AI strategy, principles, roadmaps, MLOps plans, or executive docs.
Use when coaching technical leaders on conflict, burnout, cofounders, CTO transitions, or growth.
Use when drafting ML/AI papers, verifying citations, framing evidence, using LaTeX, or preparing submissions.
Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis.
| name | manning-tech-book-writing |
| description | Use when writing Manning-style technical chapters, Chapter 1s, examples, callouts, or summaries. |
| allowed-tools | Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch |
Use for Manning-style technical book chapters. Move readers from concrete examples to useful mental models with minimal theory up front.
Define the reader, chapter goal, and skills gained. Open with 3-5 "This chapter covers" bullets, start from a concrete problem, introduce concepts just in time, and close with complete-sentence summary bullets.
Chapter 1 must answer what the technology is, why the reader should care, and how it works end to end. Use one clear mental model with a simple scenario, component diagram, data flow, and explanatory caption.
Review for early practical value, concrete examples, motivated theory, explained code, correct callout/sidebar use, and AI-writing artifacts.
Load Chapter 1, structure, style, opening/summary, callout/sidebar, introduction, or file-naming references only when the task needs that detail.
