Prose Style

Apply when writing or editing prose meant for humans to read — READMEs, docs, comments, commit messages, PR descriptions, user-facing text. Not for code itself or structured data.

p7th0n Updated

File contents

Prose style

Style rules

  • Sentences: 10-20 words average, 30-word ceiling
  • Paragraphs: one idea, 2-4 sentences
  • Bullets for 3+ discrete items; prose for everything else
  • Reading level: 8th-10th grade unless technical precision requires otherwise
  • State each idea once — reference it later, don't restate it

Editorial pass (run after drafting, before presenting)

  1. Cut any sentence that adds no new information
  2. Split anything over 30 words
  3. Replace jargon where a plain term works without losing precision
  4. Find repeated points — keep the clearest instance, cut the rest
  5. Confirm every paragraph earns its place

When rules conflict with precision

Technical accuracy wins. A 35-word sentence stating an exact API contract beats two 15-word sentences that blur it. Flag the tradeoff rather than silently over-simplifying.

p7th0n/claude_public_skills/tree/main/prose-style commit 017463ce33

Frequently asked questions

npx skillmds@latest add p7th0n/prose-style