skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

writing-user-facing-copy

Enforces voice, tone, and naming rules for user-facing product copy.

713|118|Updated Aug 11, 2020
Search Tags:#style guide#copywriting#ux writing#tone of voice#editorial#PostHog#ui text
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill writing-user-facing-copy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-user-facing-copy
Source: https://github.com/PostHog/posthog-foss/tree/main/.agents/skills/writing-user-facing-copy
Command: npx skills add https://github.com/PostHog/posthog-foss --skill writing-user-facing-copy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent tone, marketing hype, and confusing feature names slip into UI text, error messages, and docs, degrading the user experience. This Skill acts as an editorial gate that standardizes every string a person reads in PostHog.

Core Features & Use Cases

  • Voice enforcement: Applies sentence case, plain language, American spelling, and a neutral humane tone while banning editorializing words like "seamless" or "powerful".
  • Style rules: Prohibits em-dashes, punchy antithesis constructions, and clever one-liners, and requires errors and empty states to point to a next step.
  • Feature naming guidance: Carries hard-to-remember naming rules, such as calling the setup tool "Wizard" only as a proper name and "the setup agent" everywhere else.
  • Use Case: Before merging a pull request that adds a new tooltip or error message, run this Skill to rewrite the string so it matches PostHog's copy standards.

Quick Start

Review and rewrite the user-facing strings in my code change so they follow the PostHog copy guidelines.

Frequently Asked Questions about writing-user-facing-copy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user-facing copy that matches PostHog's voice?▼

Use sentence case, plain language, and a neutral humane tone. State what happened and what to do next, avoid editorializing words like "seamless" or "powerful", and use American English spelling throughout.

What tone rules apply to UI labels and error messages?▼

UI text must be direct and friendly without sales-y or edgy phrasing. Error and empty states must say what happened and give a next action, never just reporting that something failed.

Can I use em-dashes in product copy?▼

No, em-dashes and en-dashes are banned in user-facing copy. Rewrite the sentence, or use a hyphen with spaces, a comma, a colon, or split it into two sentences.

How should I refer to the Wizard feature in copy?▼

Use "Wizard" only as the feature's proper name. When explaining what it does, call it "the setup agent" or "the agent", since "wizard" suggests an old-style step-by-step form rather than an AI.

When should this copy skill not be applied?▼

Do not apply it to developer-only text such as code comments, commit messages, log lines, or variable and function names. It governs only strings a user will actually read.

Related Skills

Explore More Content & Communication Skills→
NuGetNuGet
822

breaking-change

Files .NET breaking-change documentation issues and drafts notification emails for labeled NuGet changes.

Official
Intermediate
tayiorbeiitayiorbeii

gstack-ship

Convert deploy requests into deterministic release workflows with tests and review gates.

Community
Advanced
dhruvil7797dhruvil7797

clarify

Rewrite unclear UX copy, error messages, labels, and instructions across interfaces.

Community
Intermediate
elasticelastic
71

docs-check-style

Validate documentation content against the Elastic style guide with Vale.

Official
Intermediate