japanese-tech-writing

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

3|Updated Jul 1, 2016
One-click install
npx skills add https://github.com/shomatan/dotfiles --skill japanese-tech-writing-shomatan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: japanese-tech-writing
Source: https://github.com/shomatan/dotfiles/tree/main/dot_claude/skills/japanese-tech-writing
Command: npx skills add https://github.com/shomatan/dotfiles --skill japanese-tech-writing-shomatan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical manuscripts often suffer from weak paragraph logic, redundant phrasing, LLM-style filler expressions, and unnatural translation-influenced metaphors. This Skill provides a comprehensive style guide that governs how Japanese technical documents, book chapters, and articles should be written and revised. ## Core Features & Use Cases - Paragraph and Argumentation Rules: Enforces paragraph writing discipline, one-topic-per-paragraph structure, explicit logical connectors, and rigorous reasoning without logical gaps. - LLM Expression Detection: Prohibits hollow LLM-style phrases (e.g., empty emphasis, formulaic transitions) and translation-influenced metaphors like literal renderings of English idioms (carry, open, live in). - Redundancy Elimination: Removes repeated claims, decorative sentences, and unnecessary rhetorical devices while preserving necessary logical scaffolding. - Use Case: When drafting a chapter of a Japanese technical book or revising a draft article, apply these norms to produce prose with tight argumentation, controlled reader cognitive load, and natural Japanese phrasing. ## Quick Start Review and rewrite this Japanese technical draft according to the japanese-tech-writing 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 improve Japanese technical writing style?

Apply paragraph writing discipline with one topic per paragraph, explicit logical connectors between paragraphs, and single-direction argumentation. Remove redundant restatements, hollow emphasis words, and translation-influenced metaphors while preserving necessary logical scaffolding.

What are common LLM-style phrases to avoid in Japanese writing?

Avoid empty announcements like "重要なのは〜である", formulaic transitions like "〜において", hollow adjectives like "不可欠" or "多角的", and vague verbs like "掘り下げる" or "言語化する" that add no substantive content to the argument.

How do I fix translation-influenced metaphors in Japanese text?

Identify expressions where English idioms were translated literally, such as "選好を運ぶ" (carry) or "問いが開かれている" (open question). Rewrite them with concrete subjects and plain Japanese verbs, like "選好がベクトルとして表現される" or "まだ答えが出ていない".

When should hedging expressions be kept in technical writing?

Keep hedging expressions like "かもしれない" or "だろう" when they represent genuine uncertainty, unverified possibilities, character recognition, reader doubts, or counterfactuals. Remove them only when the claim is already established by evidence in the text.

What are the limitations of this writing style guide?

The guide targets Japanese technical prose such as book chapters, articles, and explanatory documents. It does not cover other languages, fiction writing, marketing copy, or document formatting concerns like layout and typography.