technical-writing ยท diff
v1.0.0 to v1.0.0
16 added, 16 removed. Audit A to A.
---
name: technical-writing
license: MIT
metadata:
version: "1.0.0"
description: |
- USE FOR: Prose QA, Vale/Harper, terminology, English/Japanese editing,
- English-to-Japanese, glossary, rhythm, AI-slop cleanup, publication QA.
+ 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.
---
# Technical Writing
- Owns meaning-preserving editing, translation, terminology, AI-slop cleanup,
- rhythm, and QA. Translation: clean source English, then render natural
- Japanese.
+ Owns meaning-preserving editing, translation, terminology, rhythm, and QA.
## 1. Workflow
- 1. Identify surface: English docs, Japanese prose, translation, skill text, or
- QA.
+ 1. Identify surface: English, Japanese, translation, skill text, or QA.
2. Preserve meaning. Do not rewrite commands, identifiers, product
names, paths, code, links, versions, or APIs for style.
- 3. For generic/AI-like prose, read
+ 3. Keep glossary/terminology polish here when meanings are stable; use
+ `clarify-concepts` first when they are not.
+ 4. For generic/AI-like prose, read
[Prose Review](references/prose-review.md).
- 4. For English checks, read
+ 5. For English checks, read
[Vale And Harper](references/vale-and-harper.md).
- 5. For English-to-Japanese, clean English first, then read
+ 6. For English-to-Japanese, clean English first, then read
[English-to-Japanese Workflow](references/english-to-japanese-workflow.md)
and [Japanese Writing Style](references/japanese-writing-style.md).
- 6. For Japanese editorial review, read
+ 7. For Japanese editorial review, read
[Japanese Writing Style](references/japanese-writing-style.md).
- 7. For accurate but flat explanatory prose, read
+ 8. For flat explanatory prose, read
[Cognitive Rhythm](references/cognitive-rhythm.md). Build rhythm from
- source material, not meta-commentary.
- 8. Apply only clarity changes; preserve facts and intent.
+ source material.
+ 9. 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.
+ 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](references/vale-and-harper.md)
- [English-to-Japanese Workflow](references/english-to-japanese-workflow.md)
- [Japanese Writing Style](references/japanese-writing-style.md)
- [Prose Review](references/prose-review.md)
- [Cognitive Rhythm](references/cognitive-rhythm.md)