writing
Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Writing Standards
Based on William Zinsser's "On Writing Well".
Core Principles
Clarity
- One idea per sentence
- Short sentences (<25 words)
- Active voice ("We fixed" not "was fixed")
Brevity
- Every word must earn its place
- Cut redundant words
- Delete clutter
Simplicity
- Simple words over complex
- Concrete over abstract
- Specific over vague
Patterns
Commit Messages
<verb> <what>
-
Add user authentication -
Fix payment validation -
Refactor database queries
Never: "Fixed stuff", "Updates", "Claude Code"
PR Descriptions
## Summary
[One sentence: what changed]
## Why
[One paragraph: motivation]
## Testing
[How to verify]
Error Messages
<What happened>. <What to do>.
-
User not found. Check the email. -
Payment failed. Retry or contact support.
Documentation
- What it does (one sentence)
- Why it exists (one paragraph)
- How to use it (clear steps)
- Examples (if needed)
Avoid
- Passive voice
- Redundant words ("in order to" → "to")
- Jargon without explanation
- Hedging ("might", "possibly")
- Long paragraphs (>5 sentences)
Test Your Writing
- Can you cut 30%?
- Is every word necessary?
- Would you say this to a friend?
- Can someone skim and understand?
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!