From hunch
Use when writing prose a human will read — docs, READMEs, PR descriptions, commit messages, code comments, chat replies, explanations. Not for code, identifiers, API names, error strings, or established technical terms.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hunch:plainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The reader lacks your context — the curse of knowledge, not word count, is why prose fails. Write as if orienting someone's gaze to a thing they haven't seen yet.
The reader lacks your context — the curse of knowledge, not word count, is why prose fails. Write as if orienting someone's gaze to a thing they haven't seen yet.
| Defect | Fix | Example |
|---|---|---|
| Zombie noun — an action embalmed as a noun (-tion, -ment, -ance) | Verb it | "perform validation" → "validate" |
| Buried doer — abstract subject, actor missing or in a by-phrase | Doer as subject, action as verb | "the fix was applied" → "I fixed it" |
| Negative form | State it positively | "not different" → "the same" |
| Hedge — "somewhat", "fairly", "arguably", "should probably" | Cut it or commit | "should probably work" → "works" — or name when it fails |
| Abstract where concrete exists | Name the thing | "the relevant file" → "config.ts" |
| One sentence, two ideas | Split it | — |
Technical terms: swap in an everyday word only where precision survives; otherwise keep the term — rule 5 yields to rule 6.
Simplified Technical English adds what Orwell leaves to judgment: hard limits. Caps over taste — "cut what you can" ends in negotiation; a word count ends in a number.
| Cap | Limit |
|---|---|
| Sentence | 20 words for an instruction, 25 for anything else |
| Paragraph | 6 sentences, one topic |
| Instruction | one action per sentence |
| Noun cluster | 3 nouns — break longer ones with "of"/"for" |
| Term | one per concept — reuse the exact word, never a synonym |
| Point | made once — no restating in other words, no summary that repeats the body |
The 900-word STE dictionary stays out: the technical-terms rule above already governs word choice.
One sweep of the draft against the spine, the sweep, and the caps. Rule 6 breaks every tie: clarity beats compliance.
npx claudepluginhub saadshahd/moo.md --plugin hunchApplies clear-writing standards to prose including READMEs, docs, UI copy, error messages, commits, and release notes. Use when writing or editing any text a human will read.
Applies Strunk's Elements of Style to draft and revise long-form documents—documentation, READMEs, guides, specs, blog posts, proposals—for clarity and conciseness. Excludes code-adjacent text like commit messages.
Writes and rewrites human-facing prose including documentation, READMEs, guides, blog posts, emails, Slack messages, PR descriptions, and release notes.