write-natural-japanese

Identify source-language interference such as English nominalization, word-for-word correspondences, and unnecessary English generalities, then reconstruct sentences around what actually happens. Preserve code, identifiers, formal product names, and established technical terms while replacing vague metaphors with concrete descriptions of behavior, conditions, and results.

Translate each expression according to its stated role in context rather than applying fixed Japanese labels. For example, render a generic API contract as the specific output requirement or compatibility condition it represents, and keep formally defined terms like DeployGuard Quality Gate unchanged.

Do not use it for ordinary Japanese responses during coding or Q&A, mechanical proofreading of typos and punctuation, editing that only concerns document structure or argumentation, or detecting AI-generated text. It applies only when natural Japanese prose is the primary deliverable.

The Skill explicitly forbids changing facts, claims, reasoning, certainty levels, or scope for the sake of naturalness. When naturalness conflicts with technical accuracy, accuracy is preserved and supplementary explanation is added instead.

No, the wording reference is not a banned-word list. Each flagged expression is evaluated in context: established terms like contract testing and Quality Gate are kept, while generic uses are concretized into the actual requirement, check, approval, or control they represent.