writing-clearly-and-concisely

To improve clarity and conciseness in technical documentation, this skill applies Strunk's style rules to enforce active voice, definite language, and concrete phrasing. It rewrites prose to reduce wordiness and ambiguity for human readers.

The best way to rewrite commit messages and error messages is by applying Strunk's timeless style rules. This enforces active voice and vigorous phrasing, transforming vague text into clear, direct, and professional communication.

Applying Strunk's elements of style improves UI text and reports by enforcing conciseness and concrete language. This consistent application reduces ambiguity and enhances comprehension across all user-facing interfaces and explanations.

Yes, you can use this skill for drafting README files and technical explanations. It guides rewriting through a simple drafting workflow that applies active voice and definite language to meet high clarity standards.

You should use active voice and concrete phrasing for documentation writing because they promote direct, vigorous sentences. This reduces wordiness and ambiguity, ensuring your technical explanations become clearer and more professional.

This style editing approach works for general human-readable prose, including documentation, reports, and UI text. It applies Strunk's rules universally to improve clarity, definiteness, and conciseness across any writing format.