japanese-tech-writing

Apply standardized Japanese technical writing rules to chapters and articles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Japanese technical writing often suffers from inconsistent formatting, unclear argumentation, and ambiguous tone. This guide defines a structured set of conventions to improve clarity and maintainability when drafting chapters, manuals, and articles in Japanese.

Core Features & Use Cases

  • Structured formatting: enforce one sentence per line, blank-line paragraph breaks, and clear separation of code blocks, footnotes, and quotations.
  • Argumentation and clarity: emphasize one-topic-per-paragraph, explicit transitions, and avoidance of hedging or vague phrasing.
  • Wide applicability: suitable for chapters, explanations, and technical documentation drafts, from initial outlines to revised manuscripts.

Quick Start

Draft a Japanese technical document following these norms.

Frequently Asked Questions about japanese-tech-writing

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

FAQPage Schema
What are the standard formatting rules for Japanese technical writing?

Standard Japanese technical writing formatting requires one sentence per line, blank-line paragraph breaks, and clear separation of code blocks, footnotes, and quotations. This structured approach enforces consistent document structure across technical chapters and articles.

How do I structure paragraphs in Japanese technical documentation?

Structure Japanese technical documentation paragraphs by enforcing one-topic-per-paragraph rules, using explicit transitions, and avoiding hedging or vague phrasing. This paragraphing approach maintains clear argumentation and improves readability in drafts and manuals.

What is the best way to handle tone and rhetoric in Japanese technical articles?

The best way to handle tone in Japanese technical articles is to apply restrained rhetoric and explicit tone guidance. Avoiding ambiguous phrasing and hedging ensures clarity and maintainability when drafting technical explanations and chapters.

Can I use these Japanese writing guidelines for technical manuals and code explanations?

Yes, these Japanese writing guidelines are suitable for technical manuals, code explanations, and chapter drafts. They apply standardized rules across structured formatting, bold section headers, and citation usage to improve documentation consistency.

Why does my Japanese technical writing have inconsistent formatting and unclear argumentation?

Japanese technical writing often suffers from inconsistent formatting and unclear argumentation due to a lack of standardized conventions. Applying explicit rules for paragraphing, code blocks, and footnotes resolves these ambiguities and improves clarity.