skills.rest
masakinihirota
masakinihirotaCOMMUNITY
Explore all skills by this author →
𝕏@masakinihirotaGitHub

writing-style

Enforces consistent Japanese writing style rules for technical documentation and articles.

Updated Jul 21, 2026
Search Tags:#documentation#writing style#markdown#technical writing#japanese#proofreading#hatena blog
One-click install
npx skills add https://github.com/masakinihirota/2026src-ni --skill writing-style-masakinihirota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-style
Source: https://github.com/masakinihirota/2026src-ni/tree/main/.agents/skills/writing-style
Command: npx skills add https://github.com/masakinihirota/2026src-ni --skill writing-style-masakinihirota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Japanese technical writing often suffers from inconsistent tone, mixed sentence styles (ですます vs である), vague expressions, and incorrect notation of product names, which reduces readability and professionalism. ## Core Features & Use Cases - Style Consistency Rules: Enforces ですます tone, sentence length limits (under 200 characters), active voice, and conclusion-first structure. - Notation Guidelines: Standardizes hiragana usage for formal nouns and auxiliary verbs, correct official product name spelling (Go, Docker, Spring Boot), and proper symbol usage. - Hatena Blog & Markdown Rules: Covers blank line placement, bold formatting without surrounding spaces, and descriptive link text. - Use Case: When drafting a Japanese technical blog post about a new API, apply this Skill to review the draft and fix mixed sentence styles, vague expressions like 〜と思う, and incorrect product name capitalization. ## Quick Start Review this Japanese technical article draft and fix any style, notation, or structure issues according to the writing guidelines.

Frequently Asked Questions about writing-style

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

FAQPage Schema
How do I keep Japanese technical writing style consistent?▼

Use the ですます tone throughout and avoid mixing it with である style. Keep sentences under 200 characters, prefer active voice, and structure content conclusion-first followed by reasons and details.

What are the rules for writing Japanese technical blog posts?▼

Key rules include using written expressions instead of colloquial ones, avoiding vague phrases like 〜と思う, writing formal nouns and auxiliary verbs in hiragana, and spelling product names exactly as official sources (Go, Docker, Spring Boot).

How should I format Markdown for Hatena Blog?▼

Insert blank lines between paragraphs, around lists, and around code blocks. Do not add half-width spaces around bold markers, and use descriptive link text instead of vague words like こちら.

When should hiragana be used instead of kanji in Japanese writing?▼

Write formal nouns (こと, ため, ところ) and auxiliary verbs (〜ください, 〜いただく, 〜できる) in hiragana. This improves readability and follows standard Japanese technical writing conventions.

What are the limitations of a writing style guideline skill?▼

It provides rules and a review checklist but does not automatically rewrite text or verify factual accuracy. Writers must still apply judgment for context-specific tone and confirm official product names against source sites.

Related Skills

Explore More Content & Communication Skills→
atman-33atman-33

tech-article-humanizer

Rewrite technical drafts into human-like Japanese articles.

Community
Advanced
yasushiasahiyasushiasahi

Technical Writing

Generate structured patterns and guidelines for technical content in English and Japanese.

Community
Intermediate
williacjwilliacj
3

grammar

Proofread theological writing for grammar, spelling, and style in US English.

Community
Intermediate
thktthkt
11

kousei

Correct and proofread Japanese text using textlint and AI structural analysis.

Community
Intermediate