japanese-tech-writing

Enforces Japanese technical writing style rules for drafting and revising documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical manuscripts often suffer from inconsistent formatting, weak argumentation, redundant phrasing, and LLM-style filler expressions. This Skill provides a comprehensive style guide that governs how Japanese technical documents, book chapters, and articles are written and revised. ## Core Features & Use Cases - Formatting Rules: Enforces one-sentence-per-line layout, footnote usage, bold for first-term definitions, and bans dashes and middle dots in Japanese prose. - Argumentation Standards: Applies paragraph writing principles, logical connectives, single-direction argument flow, and rigor checks that preempt reader objections. - Style Enforcement: Prohibits LLM-style empty phrases, redundant restatement, excessive dramatization, and vague hedging while preserving legitimate uncertainty markers. - Use Case: When drafting a chapter of a Japanese technical book or revising a draft article, apply these rules to produce prose with clear paragraph structure, precise terminology, and no filler. ## Quick Start Revise this Japanese technical draft according to the japanese-tech-writing style rules and fix formatting, argumentation, and redundant expressions.

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 Japanese technical documents with consistent style?

Apply a defined style guide covering formatting, paragraph structure, and terminology. This Skill enforces one-sentence-per-line layout, bold for first-term definitions, footnotes for asides, and paragraph writing principles where each paragraph advances one logical step.

How to revise Japanese technical writing to remove LLM-style phrases?

Identify and remove empty expressions like "重要なのは〜である", "正面から扱う", "掘り下げる", and unfounded hedges like "〜と言えるだろう". Replace them with direct statements of the actual claim, keeping only uncertainty markers that express genuine possibility or reader doubt.

What formatting rules apply to Japanese technical manuscripts?

Key rules include one sentence per line with blank lines between paragraphs, code blocks for code and logs, footnotes for tangential notes, no em dashes or middle dots in prose, and headings that name a single specific topic rather than compound phrases.

When should hedging expressions be kept in Japanese technical writing?

Keep hedges like "かもしれない" and "だろう" 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 cause.

What are the limitations of a style-guide-only writing skill?

This Skill contains only prose rules in SKILL.md with no scripts or automated checks, so enforcement depends entirely on the AI applying the guidelines during writing or revision. It does not lint files, detect violations programmatically, or integrate with textlint or other Japanese proofreading tools.