Technical Writing
Owns meaning-preserving editing, translation, terminology, rhythm, and QA.
1. Workflow
- Identify surface: English, Japanese, translation, skill text, or QA.
- Preserve meaning. Do not rewrite commands, identifiers, product
names, paths, code, links, versions, or APIs for style.
- Keep glossary/terminology polish here when meanings are stable; use
clarify-concepts first when they are not.
- For generic/AI-like prose, read
Prose Review.
- For English checks, read
Vale And Harper.
- For English-to-Japanese, clean English first, then read
English-to-Japanese Workflow
and Japanese Writing Style.
- For Japanese editorial review, read
Japanese Writing Style.
- For flat explanatory prose, read
Cognitive Rhythm. Build rhythm from
source material.
- Apply only clarity changes; preserve facts and intent.
2. Boundaries
Issue 225/226 boundaries: no automation, model/cost/privacy,
external-sharing approval, derivative publication approval, or chunking.
Do not add direct polished-Japanese drafting from scratch. Repair English
first, then translate or QA Japanese.
3. References
- Vale And Harper
- English-to-Japanese Workflow
- Japanese Writing Style
- Prose Review
- Cognitive Rhythm
1---2name: technical-writing3description: USE FOR: Prose QA, Vale/Harper, terminology, English/Japanese edits, English-to-Japanese, stable glossaries, rhythm, AI-slop cleanup, publication QA. DO NOT USE FOR: AI detector/humanizer workflows, fresh generation, meaning-changing rewrites, replacing author judgment, publishing, model/cost/privacy, external sharing, or chunking.4license: MIT5---67# Technical Writing89Owns meaning-preserving editing, translation, terminology, rhythm, and QA.1011## 1. Workflow12131. Identify surface: English, Japanese, translation, skill text, or QA.142. Preserve meaning. Do not rewrite commands, identifiers, product15 names, paths, code, links, versions, or APIs for style.163. Keep glossary/terminology polish here when meanings are stable; use17 `clarify-concepts` first when they are not.184. For generic/AI-like prose, read19 [Prose Review](references/prose-review.md).205. For English checks, read21 [Vale And Harper](references/vale-and-harper.md).226. For English-to-Japanese, clean English first, then read23 [English-to-Japanese Workflow](references/english-to-japanese-workflow.md)24 and [Japanese Writing Style](references/japanese-writing-style.md).257. For Japanese editorial review, read26 [Japanese Writing Style](references/japanese-writing-style.md).278. For flat explanatory prose, read28 [Cognitive Rhythm](references/cognitive-rhythm.md). Build rhythm from29 source material.309. Apply only clarity changes; preserve facts and intent.3132## 2. Boundaries3334Issue 225/226 boundaries: no automation, model/cost/privacy,35external-sharing approval, derivative publication approval, or chunking.3637Do not add direct polished-Japanese drafting from scratch. Repair English38first, then translate or QA Japanese.3940## 3. References4142- [Vale And Harper](references/vale-and-harper.md)43- [English-to-Japanese Workflow](references/english-to-japanese-workflow.md)44- [Japanese Writing Style](references/japanese-writing-style.md)45- [Prose Review](references/prose-review.md)46- [Cognitive Rhythm](references/cognitive-rhythm.md)
i9wa4