japanese-tech-writing

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical manuscripts often suffer from weak paragraph logic, LLM-style empty phrases, translation-flavored metaphors, and redundancy. This Skill provides a comprehensive style guide that keeps chapters, articles, and drafts logically rigorous and readable. ## Core Features & Use Cases - Paragraph and Argumentation Rules: Enforces paragraph writing with one topic per paragraph, explicit logical connectors, and single-pass conclusions. - LLM Phrase Detection: Bans empty LLM-style expressions such as "正面から扱う", "掘り下げる", and hollow intensifiers, plus translation-flavored metaphors like 「運ぶ」「開かれた問い」. - Reader Load Management: Controls information density, unnecessary proper nouns, and redundancy to reduce reader cognitive load. - Use Case: When drafting or revising a chapter of a Japanese technical book, apply this Skill to rewrite passages so each paragraph advances one logical step and contains no LLM-sounding filler. ## Quick Start Use the japanese-tech-writing skill to review and rewrite this Japanese technical 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 improve Japanese technical writing style?

Apply paragraph writing principles: one topic per paragraph, a topic sentence first, and explicit logical connectors between paragraphs. Then remove LLM-style empty phrases, translation-flavored metaphors, and redundant restatements of the same claim.

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

Avoid empty announcements like 「重要なのは〜である」「正面から扱う」, hollow adjectives like 「不可欠」「多角的」, and vague verbs like 「掘り下げる」「言語化する」. These add a feeling of thoroughness without adding content.

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

Check whether a reader could imagine the literal action, such as 運ぶ, 開く, or 住む. If so, rewrite with concrete subjects and objects, for example changing 「ベクトルが選好を運ぶ」 to 「選好がベクトルとして表現される」.

Should all hedged expressions like かもしれない be removed?

No. Keep hedges that express genuine uncertainty, hypotheses, reader doubts, or characters' perceptions. Only remove hedging that weakens claims already established by evidence in the text.

When should bold emphasis be used in Japanese technical documents?

Limit bold to one or two places per section, reserved for logical keystones such as negations that prevent misreading or section conclusions. Everything else should be emphasized through sentence order and structure.