What problem does it solve? Project prose drifts into vague, unverifiable, or overly ornate wording: rules padded with justification, claims about the future, facts recalled from memory instead of checked, and metaphors that read poorly. This Skill enforces a consistent documentation style so every rule, spec item, README section, and code comment states what is true in plain, checkable language. ## Core Features & Use Cases - One-sentence rules: Keeps each rule to a single verifiable sentence, moving justification and alternatives into a separate pitfalls section. - Fact verification discipline: Requires checking code, branches, and command output directly rather than writing numbers or behavior from memory. - Glossary workflow: Defines a four-step process for introducing new terms, including searching rejected words before adding new ones. - Use Case: When drafting a spec item like "a booking has at least one adult," the Skill guides you to drop implementation details (database constraints, write paths), avoid future claims, and phrase it as a single testable statement. ## Quick Start Ask the assistant to review or rewrite a rule, spec item, README paragraph, or code comment using the doc-style wording conventions.
