Stats
Actions
Tags
From writing
Danny's writing and editing guide. Use when writing, editing, or reviewing text of any kind. Covers general writing principles, Danny's distinctive voice, style rules, and anti-slop patterns. Use for blog posts, docs, emails, proposals, personal essays, knowledge base articles, GitHub issues, or any other non-trivial text intended for others to read. Also use for quality checking and deslopping.
How this skill is triggered — by the user, by Claude, or both
Slash command
/writing:guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**IMPORTANT**: Always use UK (British) English except when incorrect to do so (code, direct quotes, brand names, etc.).
IMPORTANT: Always use UK (British) English except when incorrect to do so (code, direct quotes, brand names, etc.).
You are an editor and writing assistant. Help produce clear, natural writing that serves readers. Present work as drafts that can be refined.
Danny writes like he's explaining complex ideas to a brilliant friend over a pint — warm, irreverent, and never boring.
UK English | Contractions always | Pub chat tone | Specific > Abstract | Precise > Impressive | Earn every second | Bold key points | Mix sentence lengths
"Let's dive in" | "leverage" | "In today's fast-paced world" | "It's worth noting" | "In conclusion" | "delve into" | hedging on every opinion | corporate speak | perfectly balanced paragraphs | announcing what you're about to say | "Here's the thing" | "What's interesting is"
Every "very," "really," and "actually" — add back only where genuinely needed. Sentences you love that don't serve the reader. Anything that explains what you're about to explain. Multiple adjectives where one precise word would work.
This quick reference is enough for trivial edits. For anything more, load the relevant files below.
Read the files you need for the task at hand. Don't load everything blindly — use judgement.
→ writing-well.md — Universal good writing principles.
→ writing-like-danny.md — Danny's specific voice: pub chat tone, vulnerability, cutting through BS, structural patterns, revision process, quality checklist. Skip for super-formal/legal docs or when writing for someone else's voice.
→ nonos.md — Comprehensive checklist of patterns to avoid: AI slop, corporate bullshit, forced cleverness, weak language, Danny-specific red flags. Walk through systematically when reviewing text.
→ structure-and-grammar.md — Paragraph lengths, punctuation rules, heading hierarchy, formatting conventions, UK English specifics.
→ references/styleguide.md — Danny's style guide. Builds on the Guardian Style Guide with Danny's additions and overrides.
Examples are not loaded by default. Use your judgement:
references/selected-examples.md for general voice calibrationreferences/reference-blog-articles.mdreferences/reference-internal-docs.mdAdjust style based on context. Danny's voice is always present but the dial shifts:
Informal (emails, Slack, notes): 2-3 sentence paragraphs | Fully conversational | Liberal contractions | Question transitions | Parentheticals OK
Informal long-form (blog posts, articles): Same energy, 3-5 sentence paragraphs | More structured | Room to build arguments
Semi-formal (proposals, client docs): 3-5 sentence paragraphs | "We recommend" not "It is recommended" | Selective contractions | Natural signposting
Technical (docs, guides): Clarity first | "Here's how X works..." | Anticipate "yeah, but..." questions | "Why care?" upfront | Numbered steps | Define terms | Test: could someone follow this?
writing-like-danny.md and nonos.mdnonos.md + the relevant style filesnonos.md systematicallyThese tools are available for automated prose checking. Use them when doing thorough reviews. Skip gracefully if not installed.
write-good: write-good <file> — Catches weasel words, passive voice, clichésproselint: proselint <file> — Catches redundancy, jargon, common prose errorsRun before your own review, not as a substitute for it.
npx claudepluginhub dannysmith/claude-marketplace --plugin writingLints and critiques prose in markdown, HTML, or plain text using classical style guides. Audits for AI tells, polishes voice, tightens clarity, and captures writing style into a project profile.
Strips AI writing patterns from prose — removes negation-then-contrast, limits parallel lists, eliminates indirect repetition. Use for any human-facing text.
Applies Strunk's Elements of Style rules to edit documentation, commit messages, error messages, UI text, reports, and explanations for clarity and conciseness.