Mailchimp Content Practices
Application skill for Mailchimp Content Style Guide (archived awesome-guidelines capsules). For repo Markdown structure (H1, fences, wrap), load markdown-writing-practices first; apply this skill to user-facing voice, UI microcopy, and inclusive language.
Core Principle
Product copy quality is clear, person-first, and scannable, plainspoken voice, active positive sentences, inclusive terms, descriptive links, and translation-safe structure.
When to Use / NOT
- Marketing pages, in-app UI strings, help center, emails, forms, error messages, blog/product copy.
- Reviewing copy for voice, inclusivity, link text, heading hierarchy, localization.
NOT when:
- Internal repo docs where only Markdown mechanics matter,
markdown-writing-practices.
- API/code identifiers, stack naming skills.
- Legal contracts requiring non-Mailchimp house style, follow legal template.
Workflow
- Voice/tone, plainspoken, active, positive (
mailchimp-style-voice-tone.md).
- Grammar/structure, hierarchy, numbers, punctuation (
mailchimp-style-grammar-structure.md).
- Inclusive people, they/them, bias-free terms (
mailchimp-style-inclusive-people.md).
- Web/a11y/i18n, headings, links, forms, translation (
mailchimp-style-web-accessibility-i18n.md).
- Verify, read aloud; heading outline; link/descriptive text scan; word-list grep for banned terms.
Red Flags
- Passive voice by default
- Jargon without brief definition
- Negative framing when positive works
- “Click here” / “Learn more” link anchors
- Directional copy (“panel on the right”)
- Skipped heading levels for styling
- Title case on body headings when sentence case required
- Buttons without verbs
- Forms asking irrelevant personal data (e.g. gender dropdown)
- Missing or decorative-only alt text on informative images
- Exclamation points in failure/error messages
- “Guys”, ninja/rockstar/wizard, master/slave, blacklist/whitelist
- Age terms (young/old/elderly) when irrelevant
- Ambiguous once/since/right in localized strings
-ing heavy translation-bound sentences
$25 instead of 25 USD for international content
- Keyword stuffing for SEO
- Writing in mascot/character voice
- Underline or bold+italic+caps emphasis stacks
Verification
- Read-aloud pass for awkward or passive sentences
- Heading hierarchy outline (H1→H2→H3, no skips)
- Link text audit (meaningful anchors, no linked punctuation)
- grep banned terms from word list (
blacklist, guys, automagical, etc.)
- For localized strings: translation checklist (SVO, repeated parallel verbs, ambiguity scan)
- Optional: accessibility review (alt text, form labels, no direction-only instructions)
References
awesome-guidelines/references/mailchimp-style-learning-note.md
awesome-guidelines/references/mailchimp-style-voice-tone.md
awesome-guidelines/references/mailchimp-style-grammar-structure.md
awesome-guidelines/references/mailchimp-style-inclusive-people.md
awesome-guidelines/references/mailchimp-style-web-accessibility-i18n.md
Related skills
markdown-writing-practices, repo Markdown layout and fences
frontend-markup-practices, semantic HTML when copy ships in templates
1---2name: mailchimp-content-practices3description: Use when authoring or reviewing product/marketing copy, Mailchimp plainspoken voice, active positive language, inclusive people terms, sentence-case UI headings, descriptive links, a11y, and translation-safe SVO.4---56# Mailchimp Content Practices78Application skill for Mailchimp Content Style Guide (archived `awesome-guidelines` capsules). For repo Markdown structure (H1, fences, wrap), load `markdown-writing-practices` first; apply this skill to user-facing voice, UI microcopy, and inclusive language.910## Core Principle1112Product copy quality is **clear, person-first, and scannable**, plainspoken voice, active positive sentences, inclusive terms, descriptive links, and translation-safe structure.1314## When to Use / NOT1516- Marketing pages, in-app UI strings, help center, emails, forms, error messages, blog/product copy.17- Reviewing copy for voice, inclusivity, link text, heading hierarchy, localization.1819**NOT when:**2021- Internal repo docs where only Markdown mechanics matter, `markdown-writing-practices`.22- API/code identifiers, stack naming skills.23- Legal contracts requiring non-Mailchimp house style, follow legal template.2425## Workflow26271. **Voice/tone**, plainspoken, active, positive (`mailchimp-style-voice-tone.md`).282. **Grammar/structure**, hierarchy, numbers, punctuation (`mailchimp-style-grammar-structure.md`).293. **Inclusive people**, they/them, bias-free terms (`mailchimp-style-inclusive-people.md`).304. **Web/a11y/i18n**, headings, links, forms, translation (`mailchimp-style-web-accessibility-i18n.md`).315. **Verify**, read aloud; heading outline; link/descriptive text scan; word-list grep for banned terms.3233## Red Flags3435- Passive voice by default36- Jargon without brief definition37- Negative framing when positive works38- “Click here” / “Learn more” link anchors39- Directional copy (“panel on the right”)40- Skipped heading levels for styling41- Title case on body headings when sentence case required42- Buttons without verbs43- Forms asking irrelevant personal data (e.g. gender dropdown)44- Missing or decorative-only alt text on informative images45- Exclamation points in failure/error messages46- “Guys”, ninja/rockstar/wizard, master/slave, blacklist/whitelist47- Age terms (young/old/elderly) when irrelevant48- Ambiguous once/since/right in localized strings49- `-ing` heavy translation-bound sentences50- `$25` instead of `25 USD` for international content51- Keyword stuffing for SEO52- Writing in mascot/character voice53- Underline or bold+italic+caps emphasis stacks5455## Verification5657- Read-aloud pass for awkward or passive sentences58- Heading hierarchy outline (H1→H2→H3, no skips)59- Link text audit (meaningful anchors, no linked punctuation)60- grep banned terms from word list (`blacklist`, `guys`, `automagical`, etc.)61- For localized strings: translation checklist (SVO, repeated parallel verbs, ambiguity scan)62- Optional: accessibility review (alt text, form labels, no direction-only instructions)636465## References6667- `awesome-guidelines/references/mailchimp-style-learning-note.md`68- `awesome-guidelines/references/mailchimp-style-voice-tone.md`69- `awesome-guidelines/references/mailchimp-style-grammar-structure.md`70- `awesome-guidelines/references/mailchimp-style-inclusive-people.md`71- `awesome-guidelines/references/mailchimp-style-web-accessibility-i18n.md`7273## Related skills7475- `markdown-writing-practices`, repo Markdown layout and fences76- `frontend-markup-practices`, semantic HTML when copy ships in templates