japanese-tech-writing

Enforces Japanese technical writing norms for drafting and revising technical documents.

Updated Dec 25, 2021

Search Tags:#editing #technical writing #japanese #style guide #proofreading #llm detection #paragraph writing

Ready to run

npx skills add https://github.com/kotahashihama/dotfiles --skill japanese-tech-writing-kotahashihama

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: japanese-tech-writing
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/japanese-tech-writing
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill japanese-tech-writing-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical manuscripts often suffer from weak paragraph logic, LLM-style filler phrases, translation-flavored metaphors, and redundancy. This Skill provides a comprehensive style guide that keeps Japanese technical prose rigorous, readable, and free of common AI-generated writing artifacts. ## Core Features & Use Cases - Paragraph and Argumentation Rules: Enforces paragraph writing discipline, one-topic-per-paragraph structure, explicit logical connectors, and rigorous reasoning without loose ends. - LLM-ism and Translation-Tone Elimination: Bans empty filler phrases (e.g., "正面から扱う", "掘り下げる"), literal translations of English idioms ("運ぶ", "開かれた問い"), and inanimate-subject personification. - Reader Load Management: Controls how much new information each paragraph introduces, avoids unnecessary proper nouns, and manages redundancy without over-compression. - Use Case: When drafting or revising a chapter of a Japanese technical book, apply this Skill to rewrite a draft so each paragraph advances one logical step, hedged claims keep their uncertainty, and no LLM-style stock phrases remain. ## Quick Start Use the japanese-tech-writing skill to review and rewrite this Japanese technical article draft according to the style norms.

Frequently Asked Questions about japanese-tech-writing

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

FAQPage Schema

How do I write better Japanese technical documentation?▼

Apply paragraph writing discipline: one topic per paragraph, a topic sentence first, and explicit logical connectors between paragraphs. This Skill codifies these rules plus argumentation rigor, redundancy removal, and heading conventions for Japanese technical prose.

How to remove LLM-style phrases from Japanese writing?▼

The Skill lists banned LLM patterns such as "正面から扱う", "掘り下げる", "不可欠", and empty connectors like "〜において". Replace them with concrete statements of what was actually done or claimed, keeping only hedges that express genuine uncertainty.

What is translation-flavored Japanese and how do I avoid it?▼

It arises from literally translating English idioms (carry → "運ぶ", open question → "開かれた問い") and inanimate-subject constructions ("モデルは知っている"). Rewrite with concrete subjects and plain verbs, e.g., "データから分かる" instead of "データが語る".

When should hedging like "かもしれない" be kept in technical writing?▼

Keep hedges when they express unverified possibility, a character's perception, inference from logs, reader doubts, or counterfactuals. Remove them only when the claim is already established by evidence in the text and the hedge merely weakens it without basis.

Does this Skill work for English technical writing?▼

No. The rules target Japanese-specific phenomena: keigo-adjacent style issues, translation-flavored metaphors from English, Japanese paragraph conventions, and LLM patterns in Japanese generation. English writing requires a different style guide.