japanese-tech-writing

Enforces Japanese technical writing norms for structure, argumentation, and style.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Kotomiya07/skills --skill japanese-tech-writing-kotomiya07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: japanese-tech-writing
Source: https://github.com/Kotomiya07/skills/tree/main/plugins/japanese-writing/skills/japanese-tech-writing
Command: npx skills add https://github.com/Kotomiya07/skills --skill japanese-tech-writing-kotomiya07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical manuscripts often suffer from weak paragraph logic, vague argumentation, reader-hostile structure, and empty LLM-style filler phrases. This Skill provides a complete style guide that keeps chapters, articles, and explanatory prose rigorous, readable, and free of common rhetorical defects. ## Core Features & Use Cases - Formatting Rules: One sentence per line, footnotes for asides, bold for first-term definitions, and bans on dashes and middle dots in Japanese prose. - Paragraph & Argument Structure: Paragraph writing discipline, one topic per paragraph, explicit logical connectives, and one-directional argumentation. - Rigor & Reader Load: Eliminates logical gaps, overgeneralization, unsupported causality, and unnecessary proper nouns that burden the reader. - Style Control: Suppresses theatrical rhetoric, bans LLM-style empty phrases (e.g., "正面から扱う", "掘り下げる"), and removes redundancy. - Use Case: When drafting or revising a chapter of a Japanese technical book, apply these norms to restructure paragraphs, tighten causal claims, and strip filler so the manuscript reads as a coherent argument. ## Quick Start Review and rewrite this Japanese technical article draft according to the japanese-tech-writing norms, fixing paragraph structure and removing LLM-style filler.

Frequently Asked Questions about japanese-tech-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve Japanese technical writing structure?

Apply paragraph writing discipline: one topic per paragraph, a first sentence that states the topic, and explicit connectives showing logical relations between paragraphs. Keep argumentation one-directional and place conclusions only after handling objections.

What LLM-style phrases should be avoided in Japanese writing?

Avoid empty declarations like 「正面から扱う」, 「掘り下げる」, 「不可欠」, 「多角的」, and preview phrases like 「重要なのは〜である」. These add a feeling of thoroughness without content; state claims directly instead.

How should headings be written in Japanese technical documents?

Headings should identify the question the section answers or the object it treats, as a single natural phrase. Avoid procedural labels, conclusion-spoiling statements, and two-element headings joined by dashes or rules.

When should hedged expressions be kept in technical prose?

Keep hedges like 「かもしれない」 and 「だろう」 when they express genuine uncertainty, possibility, a character's recognition, inference from logs, or counterfactuals. Only remove them when the claim is already established by evidence in the text.

What formatting rules apply to Japanese technical manuscripts?

Use one sentence per line with blank lines between paragraphs, code blocks for code and logs, footnotes for tangential notes, bold for first-time term definitions, and full-width colons for term-definition lists. Avoid em dashes and middle dots in prose.