What problem does it solve? Educational articles written by multiple contributors drift in tone, terminology, and heading structure, producing inconsistent Japanese technical content. This Skill enforces a unified style guide for the Optimization Compass content corpus (content/methods, content/concepts) so every article follows the same voice, notation, and section conventions. ## Core Features & Use Cases - Style and Tone Rules: Enforces desu/masu form, one-idea-per-sentence writing, redundancy compression, and conditional phrasing for unguaranteed claims. - Terminology Normalization: Defines which terms stay in English (step, solver, gradient norm) versus Japanese (勾配, 目的関数, 凸性), plus canonical method names like BFGS and Nelder–Mead. - Heading Canonicalization: Provides a replacement table for drifting headings (e.g., Python例 → Python) and standard section orders for method, family, and concept articles. - Use Case: When revising an existing method article, apply the proofreading checklist to fix notation inconsistencies, normalize headings, update last_reviewed, and verify the first paragraph matches the frontmatter summary—without altering facts, code, math, or links. ## Quick Start Proofread the article at content/methods/bfgs.md using the article-style rules and fix any terminology or heading inconsistencies without changing technical facts.
