Skill

/writing-guidelines

Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy",

One skill from pro-workflow.

shell

$ npx -y skills add rohitg00/pro-workflow --skill writing-guidelines --agent claude-code

Installs just this skill. Get the whole plugin for auto-invocation.

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/writing-guidelines

Context preview

The summary Claude sees to decide when to auto-load this skill.

Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy",

Stats

Stars2,638

Forks255

LanguageJavaScript

Ships with pro-workflow

@rohitg00 Get the whole plugin, auto-invoked

SKILL.md

writing-guidelines.SKILL.md

---
name: writing-guidelines
description: Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
---

# writing-guidelines

Write for a reader who is busy and did not see your work. Readability beats
cleverness; clarity beats completeness.

## Rules

- **Lead with the outcome.** The first sentence answers what happened or what
  the thing is - the line the reader would ask for if they said "just the TLDR".
  Supporting detail comes after.
- **Cut filler.** Delete "just", "simply", "basically", "in order to", "it is
  important to note". If a sentence changes nothing when removed, remove it.
- **Concrete over abstract.** Name the file, the number, the command. "Faster"
  is weaker than "cuts the build from 40s to 9s".
- **Active voice, one idea per sentence.** Short sentences that each carry one
  point read faster than long ones that carry three.
- **Consistent terms.** Use the project's own vocabulary, the same word for the
  same thing every time. Tie names to the shared-language `CONTEXT.md` when one
  exists (see `domain-modeling`).
- **Readable, not clipped.** Being short and being clear are different. Achieve