write-documents

Name: write-documents
Availability: InStock
Author: sato-dev1234

Generate technical documentation with YAML frontmatter and textlint checks.

Updated Aug 23, 2026

Search Tags:#documentation #technical-writing #api-docs #user-guides #feature-specifications #japanese-writing

Ready to run

npx skills add https://github.com/sato-dev1234/claude-code-sample --skill write-documents-sato-dev1234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-documents
Source: https://github.com/sato-dev1234/claude-code-sample/tree/main/skills/write-documents
Command: npx skills add https://github.com/sato-dev1234/claude-code-sample --skill write-documents-sato-dev1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates high-quality, consistent technical documentation across APIs, features, and user guides, with emphasis on UI terminology and Japanese writing quality.

Core Features & Use Cases

API documentation generation and standardization.
Feature specifications detailing behavior, interfaces, and acceptance criteria.
User guides and onboarding materials with clear terminology and Japanese language quality.

Quick Start

Provide a ticket or project brief and I will generate polished docs following the required structure.

Frequently Asked Questions about write-documents

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

FAQPage Schema

How do I generate API documentation with consistent UI terminology and Japanese writing?▼

Generate API documentation by providing a ticket or project brief to automate structured Markdown content creation. The workflow applies consistent UI terminology and performs textlint checks to ensure high-quality Japanese technical writing across APIs, features, and user guides.

What is the best way to write feature specifications and user guides for Japanese software projects?▼

The best way to write feature specifications and user guides is using an automated workflow that loads project knowledge, generates Markdown body structures with YAML frontmatter, and validates Japanese language quality via textlint checks for consistent UI terminology.

How does automated technical writing handle Markdown structure and textlint checks?▼

Automated technical writing handles Markdown structure by fulfilling YAML frontmatter in SKILL.md files and generating a structured Markdown body. It performs textlint checks end-to-end to validate content quality and Japanese writing conventions.

Can I use this documentation generation approach for user manuals and onboarding materials requiring Japanese polish?▼

Yes, you can use this documentation generation approach for user manuals and onboarding materials. It automates clear technical documentation creation with an emphasis on UI terminology consistency and high-quality Japanese writing polish.

Do I need to provide a project brief to generate technical documentation automatically?▼

Yes, you need to provide a ticket or project brief as input. The automated workflow then loads your project knowledge to generate polished technical documentation, including API docs, feature specifications, and user manuals, following the required structure.