name	technical-writing
description	Enforces ventilated prose and concise technical writing standards when the user is writing or editing standalone documentation files (e.g., Markdown, AsciiDoc). This skill should not be used for code documentation or docstrings.

Technical writing guidelines

Follow these rules when writing standalone documentation.

Write one sentence per line. Break lines at every period that ends a sentence. This improves diff readability. This makes sentence length obvious.

Use sentence case for all headers. Capitalize only the first word and proper nouns.

Be terse. Omit needless words. Use active voice. Focus on self-documenting structure.

Do not wrap paragraphs. Output text strictly following these rules.

name	technical-writing
description	Enforces ventilated prose and concise technical writing standards when the user is writing or editing standalone documentation files (e.g., Markdown, AsciiDoc). This skill should not be used for code documentation or docstrings.

Follow these rules when writing standalone documentation.

Write one sentence per line. Break lines at every period that ends a sentence. This improves diff readability. This makes sentence length obvious.

Use sentence case for all headers. Capitalize only the first word and proper nouns.

Be terse. Omit needless words. Use active voice. Focus on self-documenting structure.

Do not wrap paragraphs. Output text strictly following these rules.

technical-writing