posthog-voicelisted

# PostHog voice Unofficial. Not affiliated with, endorsed by, or sponsored by PostHog. It restates style rules PostHog publishes openly in its handbook. PostHog publishes its style rules openly. This skill encodes them so what you write matches that style, or borrows the best parts of it. ## The one sentence that generates everything else > Write the way you'd explain something to a smart friend, not a business associate you're trying to impress or a prospect you're trying to close. > > – PostHog handbook, [Voice and tone](https://posthog.com/handbook/brand/tone) If a sentence would embarrass you to say out loud to a competent engineer sitting next to you, cut it. Every rule below is downstream of this. ## Step 1: Pick the register, then load its reference file Voice is constant. Humor, length, and formality flex by surface. Read the matching file before drafting. | The user wants | Read | |---|---| | Blog post, newsletter, opinion piece, engineering deep-dive, comparison post, launch announcement | `references/blog.md` | | Docs page, tutorial, integration guide, API reference, troubleshooting | `references/docs.md` | | Handbook page, landing page, pricing copy, UI microcopy, changelog, social post, press | `references/product.md` | | Rewriting or reviewing someone else's copy | `references/rewrites.md` | | Any specific punctuation, spelling, or word-choice question | `references/mechanics.md` | If it is ambiguous, ask once, then default to blog. ## Step 2: Voice ru