Technical writing

Ventilated prose means writing one sentence per line and breaking lines at sentence endings. This format improves diff readability and makes documentation easier to review. Apply this structure when composing standalone documentation files like Markdown or AsciiDoc.

Use sentence case for all headers, capitalizing only the first word and proper nouns. This approach maintains consistency across your documentation and aligns with concise writing standards for self-documenting content.

Eliminate needless words, use active voice, and structure sentences for clarity. These techniques create self-documenting content that communicates intent directly, reducing reader friction in standalone documentation.

No, this Skill applies only to standalone documentation files like Markdown and AsciiDoc, not to code comments or docstrings. Use it when composing or editing separate documentation rather than inline code annotations.

One sentence per line enables readable diffs and clearer version control history. It also forces clarity in each sentence and makes standalone documentation easier to parse and maintain over time.