content-style-guide
Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Content Style Guide Skill A style guide makes a brand sound like one voice no matter who's writing. The useful ones aren't 50 pages of rules — they're **voice principles with examples, tone guidance by context, and a word list** people reach for daily. This skill produces a guide a team will actually use, grounded in concrete do/don't examples rather than abstract adjectives. ## Working from a brief Given "a style guide for our fintech app", **produce the full guide anyway** — infer voice principles and terminology from the brand and audience, and mark inferred choices for the team to confirm. Make every principle **show an example**. Never hand back abstract values with no examples. ## Required Inputs Ask for these only if they aren't already provided (else infer and label): - **The brand & audience** — what you do, who you write for, and how you want to come across. - **Existing voice cues** — sample copy you like (and dislike), and any current rules. - **Surfaces** — where this applies (product UI, marketing, support, docs) — tone may shift by surface. - **Specifics** — preferred terms, things to avoid, locale (US/UK spelling), formality. ## Output Format ### [Brand] Content S
- Working from a brief
- Required Inputs
- Output Format
- [Brand] Content Style Guide
- Quality Checks
- Anti-Patterns
- Based On
What does the content-style-guide skill do?
Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.