メニュー
Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tech-writing |
| description | Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis. |
| allowed-tools | Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch |
Use for strategic technology writing: blog posts, opinion pieces, engineering narratives, and longer industry analysis. Every sentence needs a job.
Short form, 800-1,500 words, is the default. Long form, 2,000-4,000 words, is only for arguments that genuinely need scenarios, history, architecture, or several distinct implications.
State the thesis early, use specific evidence, develop only the points the thesis requires, cut repeated sections and generic examples, and end with a concrete implication.
Be opinionated, specific, concise, and technically grounded. Prefer named systems, concrete incidents, numbers, and tradeoffs over generic industry language.
../copy-editing/references/avoid-ai-writing.md?Load Radar examples, historical parallels, scenario planning, or the copy-editing AI-writing audit only when the task needs that depth.
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 writing Manning-style technical chapters, Chapter 1s, examples, callouts, or summaries.
Use when drafting ML/AI papers, verifying citations, framing evidence, using LaTeX, or preparing submissions.