writing-guide

Japanese technical documentation requires following style guidelines that enforce natural readability, such as limiting bold usage, avoiding colon endings, and including version information and concrete code examples. This Skill provides those rules to ensure human-like expression while maintaining consistency across your docs.

Apply readability and tone guidelines including limiting bold emphasis, avoiding colon line endings, including version sources, and providing concrete examples. This Skill enforces these style rules to keep technical documentation clear, consistent, and natural-sounding in Japanese.

Review documents against style guidelines, verify sources and version information are present, check that examples and code samples are concrete, and ensure the writing reads naturally without AI-generated artifacts. This Skill provides the verification rules and checklist needed for effective proofreading.

Yes. This Skill applies to any Japanese technical writing—READMEs, API docs, blog posts, and explanations. It ensures natural readability, includes sources and versions, provides concrete examples, and maintains consistent style across all technical content formats.

Apply structured style rules that enforce human-like tone, include version and source information upfront, use concrete code examples instead of generic descriptions, and review output against a readability checklist. This Skill codifies these practices to systematically eliminate AI-generated phrasing.

No. This Skill provides concrete style rules and templates for both creation and review, making it accessible whether you're writing from scratch or refining existing docs. It handles the verification checklist so you can focus on content clarity.