원클릭으로
tech-writing
Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis.
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 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.
| 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.