hayatosc/dotfiles/japanese-tech-writing

Japanese Technical Writing

Preserve the author's claims, evidence, terminology, and intended reader. Improve the text at the requested scope; do not turn a sentence edit into a chapter rewrite.

Manuscript Baseline

• Write one sentence per source line and separate paragraphs with a blank line. Use fenced blocks for code, logs, and configuration.
• Build each paragraph around one claim, supported by evidence or an example. Define terms before relying on them and preserve consistent terminology.
• Use concrete subjects and verbs. Keep necessary qualifications; remove repeated claims and empty announcements about the document.
• In Japanese prose, avoid em dashes and horizontal bars; use parentheses or sentence boundaries. Avoid middle dots for ordinary enumeration, preserving those inside proper names.
• For full manuscript work, read formatting.md. For a focused revision, read the relevant reference below and preserve the surrounding format.

• Manuscript formatting, quotations, footnotes, or columns: formatting.md.
• Paragraph logic, definitions, transitions, or reader context: argument.md.
• Voice, concrete language, restrained rhetoric, headings, or redundant phrasing: voice-and-editing.md.

Load the reference that addresses the writing problem. For a full chapter, more than one may be relevant; existing terminology and source constraints still apply.

State claims directly and connect them to evidence. Keep examples concrete, distinguish hypothetical scenarios from observed facts, and retain meaningful uncertainty. Remove empty framing without deleting context the reader needs.

Use cognitive-rhythm-writing when pacing or monotony is part of the request, not as a default additional reading requirement. Finish with the requested text or edits, noting factual gaps that could not be resolved. Do not append an unrequested editorial report.