Human Copywrite

Editorial style and usage guidance distilled from the Apple Style Guide (June 2025). Use it whenever you're producing text a human will read.

When to Apply

Trigger this skill whenever the output is text a human will read. Specifically:

• UI strings & error messages — button labels, dialog text, empty states, onboarding copy. Voice and UI-vocabulary rules apply.
• User-facing documentation — help articles, READMEs, onboarding guides, tutorials. All rules apply.
• Developer documentation — API references, SDK guides, code comments meant for humans. Add the technical-notation rules.
• Marketing copy — feature announcements, landing pages, release notes. Voice, capitalization, and product-name rules are load-bearing.
• Localized content — anything that will be translated. The international-style rules become primary.
• Writing about Apple platforms — even if the surrounding product isn't an Apple product, refer to Apple hardware/software by Apple's preferred forms (iPhone, iPad, macOS, App Store).

If the user is writing code with no user-facing strings, skip this skill. If they're writing a function name or variable, that's not copywriting — that's naming, which lives elsewhere.

Core Principles

These run through every section. When in doubt, fall back on them.