japanese-tech-writing

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill japanese-tech-writing-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: japanese-tech-writing
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/japanese-tech-writing
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill japanese-tech-writing-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Japanese technical books, articles, and documentation often suffers from inconsistent formatting, weak argumentation, redundant phrasing, and LLM-sounding filler. This Skill provides a comprehensive style guide that enforces consistent, rigorous, reader-friendly Japanese technical prose. ## Core Features & Use Cases - Formatting Rules: Enforces one-sentence-per-line layout, footnote usage, bolding of newly defined terms, and bans dashes and middle dots in Japanese prose. - Argumentation & Paragraph Structure: Applies paragraph writing principles, logical connectives, one-directional argument flow, and rigor checks that remove logical gaps. - Style & Redundancy Control: Suppresses theatrical rhetoric, bans LLM-style empty phrases, eliminates redundancy, and governs heading naming and reader honesty. - Use Case: When drafting a chapter of a Japanese technical book or revising a blog article draft, apply this Skill to rewrite the text so it follows consistent formatting, tight logic, and natural Japanese expression. ## Quick Start Rewrite this Japanese technical article draft following the japanese-tech-writing style rules for formatting, argumentation, and redundancy removal.

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 phrasing. This Skill enforces one-sentence-per-line layout, footnotes for asides, bold for newly defined terms, and paragraph writing principles so each paragraph advances one logical step.

How to remove LLM-sounding phrases from Japanese text?

Identify and delete empty formulaic expressions such as "重要なのは〜である", "正面から扱う", "掘り下げる", and unfounded hedges like "〜と言えるだろう". Replace them with direct statements of the actual claim, keeping hedges only when they express genuine uncertainty.

What punctuation should be avoided in Japanese technical writing?

Avoid em dashes and double dashes in Japanese prose and headings, and avoid middle dots for parallel listing. Use parentheses for inserted supplements, split sentences at periods for rephrasing, and use full-width colons for term-definition lists.

When should hedging expressions be kept in technical writing?

Keep hedges like "かもしれない" or "だろう" when they express genuine uncertainty, unverified possibilities, a character's perception, inference from logs, reader doubts, or counterfactuals. Only remove them when the claim is already established by evidence in the text.

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

It governs prose quality, not factual accuracy or subject-matter correctness. It does not verify technical claims, run code examples, or check citations, so domain review and testing of any code samples remain separate steps.