documentation-principles

Apply 14 principles to review, fix, and write Japanese technical documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sato-dev1234/claude-code-sample --skill documentation-principles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-principles
Source: https://github.com/sato-dev1234/claude-code-sample/tree/main/skills/documentation-principles
Command: npx skills add https://github.com/sato-dev1234/claude-code-sample --skill documentation-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This set of guidelines provides a structured approach to producing high-quality, concise, and well-visual Japanese documentation across projects by standardizing language, format, and review processes.

Core Features & Use Cases

  • Establishes a universal 14-principle framework covering Japanese quality, conciseness, visual expression, technical documentation, and project rules.
  • Guides document review, fix, and writing workflows to ensure consistency and clarity in technical documents.
  • Supports teams to quickly align on style and structure during documentation tasks.

Quick Start

Apply these principles to existing and new Japanese documentation to improve clarity and consistency.

Frequently Asked Questions about documentation-principles

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

FAQPage Schema
How do I improve the quality and conciseness of Japanese technical documentation?

To improve Japanese technical documentation quality, you can apply a structured 14-principle framework that standardizes language, format, and review processes across your projects. This ensures clarity and consistency.

What is the best way to standardize Japanese writing style for technical project docs?

Standardizing Japanese writing style involves establishing a universal framework covering conciseness, visual expression, and technical project rules. This aligns teams quickly on structure during document review and writing workflows.

Does this approach support team-level document review workflows for Japanese docs?

Yes, this approach supports team-level document review workflows by guiding fixes and writing tasks for Japanese technical documents. It helps teams align quickly on style, structure, and quality standards.

What are the limitations when applying these documentation principles to new Japanese content?

The principles require a Markdown body with frontmatter including a name and description to provide actionable guidelines. Implementation is intermediate, needing structured application to ensure concise quality across diverse technical documents.