skills.rest
robertphyatt
robertphyattCOMMUNITY
Explore all skills by this author →
GitHub

elements-of-style

Rewrite technical writing using Strunk & White principles for concise active language.

7|1|Updated Mar 26, 2026
Search Tags:#documentation#writing#clarity#conciseness#style-guide#code-comments#active-voice
One-click install
npx skills add https://github.com/robertphyatt/ironclaude --skill elements-of-style-robertphyatt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elements-of-style
Source: https://github.com/robertphyatt/ironclaude/tree/main/worker/skills/elements-of-style
Command: npx skills add https://github.com/robertphyatt/ironclaude --skill elements-of-style-robertphyatt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical writing for software and technical teams often becomes verbose, inconsistent, or hard to scan across documentation, code comments, and user-facing messages. This skill applies proven writing principles to elevate clarity, brevity, and precision everywhere your words appear.

Core Features & Use Cases

  • Apply Strunk & White's rules to documentation, commit messages, error messages, API responses, and log messages.
  • Enforce concise language, active voice, concrete detail, and positive framing to improve readability.
  • Provide practical rewrite guidance and templates for common artifacts (docs, comments, error strings).

Quick Start

Provide a paragraph you want rewritten and I will apply Strunk & White principles to produce a concise, active version.

Frequently Asked Questions about elements-of-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve technical writing clarity in software documentation?▼

Rewrite code comments for conciseness by applying Strunk & White rules to eliminate passive voice, remove redundant phrasing, and enforce concrete details with explicit verification checks.

Can I use this to rewrite verbose error messages and API responses?▼

Yes, this approach improves commit messages and logs by enforcing positive framing, active voice, and concise language, replacing verbose technical text with scannable, clear strings.

What is the best way to enforce a consistent style guide for technical writing?▼

Technical writers, developers, and software teams who need to elevate clarity, brevity, and precision across documentation, code comments, and user-facing messages can benefit from this approach.

How do I rewrite commit messages to be more concise and active?▼

Limitations include relying on the underlying Strunk & White principles, meaning highly specialized domain jargon may require manual review to ensure technical accuracy after rewriting.

Related Skills

Explore More Content & Communication Skills→
BrunoAMSilvaBrunoAMSilva

technical-communication

Enforce concise, active voice writing for API docs, code comments, and ADRs.

Community
Intermediate
eugenelimeugenelim
15

voice-and-microcopy

Draft and review user-facing UI microcopy for product interfaces.

Community
Intermediate
thimsluggathimslugga

writing-clearly-and-concisely

Rewrite verbose prose using Strunk's rules for active voice and concision.

Community
Intermediate
ghalacticghalactic

google-developer-style-guide-naming-terminology

Enforce Google developer documentation style guide capitalization, abbreviations, spelling, and grammar.

Official
Advanced