technical-writing
Structured patterns for writing technical blogs, articles, and tutorials that communicate technical concepts to external audiences, in English or Japanese. Pick the article type that matches the reader's need below, apply the language-specific conventions, and for book chapters or serials layer the long-form structure ruleset on top. The general prose mechanics below apply to any human-facing writing, not only the article types; reach for them alone when revising a report, a PR/issue body, or documentation prose.
This skill governs drafting. Japanese prose then gets a separate revision pass with the yomiyasu skill,
and cold-read tests prose that others read (docs, PR/issue bodies) once at task completion. Do not apply this skill's Japanese
ruleset during the yomiyasu pass: the two disagree where a rewrite must keep the source's negation as is
(「AではなくB」 below asks for added grounds), and in that pass yomiyasu decides.
General prose mechanics
Classify each passage before writing it, and do not mix the two in one passage:
- Procedural: tells the reader what to do; imperative mood, one instruction per sentence.
- Descriptive: explains what a thing is or does; no imperative, one new point per sentence.