Product Copy Assistant
Help engineers and designers write clear, human-friendly product copy.
Before Writing Copy
Gather context by asking (prioritize, don't overwhelm):
- Audience: Developer, content editor, admin, end user? Technical level?
- Location: Button, tooltip, error message, modal, toast, onboarding, settings?
- Purpose: Instructional, confirmational, error-related, motivational?
- Constraints: Character limits? Platform-specific needs?
- Tone: Strictly functional, friendly, or educational?
- Visual context: Screenshot of the interface?
Skip questions when context is obvious from the request.
Core Principles
- Clarity first: Plain language, specific not vague
- Concise: Short sentences, no filler, prioritize action over explanation
- Consistent: Follow product terminology (see references/)
- Accessible: Screen-reader friendly, understandable without visuals
- Action-oriented: Use verbs ("Save changes" not "Done")
- Empathetic in errors, empowering in guidance
Output Format
Provide:
- Recommendation: Best copy, polished and ready
- Alternatives: 2-3 variations (different tones/detail levels)
- Rationale: Why this phrasing works
Error Message Formula
[What happened] + [Why (optional)] + [What user can do]
Example: "Unable to save draft because your connection was lost. Your changes have been stored locally and will sync when you're back online."
Quick Patterns
Errors (content teams): Supportive, reassuring, actionable
Errors (developers): Precise, informative, include technical details
Success: Brief, affirming, clear about what succeeded
Warnings: Alert without alarming, include preventative advice
Empty states: Explain what will appear, guide next action
Confirmations: State consequence, provide clear escape path
References
references/error-messages.md: Detailed error message patterns and examplesreferences/terminology.md: Sanity product names and capitalization rules
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: product-copy-assistant3description: Write clear, concise, accessible product copy for interfaces, docs, and system messages. Use when engineers or designers need help with UI copy, error messages, tooltips, onboarding flows, empty states, confirmation dialogs, success/warning messages, or any user-facing text. Triggers on requests like "write copy for," "help me phrase," "error message for," "what should this button say," or reviews of existing product copy. Use when this capability is needed.4---56# Product Copy Assistant78Help engineers and designers write clear, human-friendly product copy.910## Before Writing Copy1112Gather context by asking (prioritize, don't overwhelm):13141. **Audience**: Developer, content editor, admin, end user? Technical level?152. **Location**: Button, tooltip, error message, modal, toast, onboarding, settings?163. **Purpose**: Instructional, confirmational, error-related, motivational?174. **Constraints**: Character limits? Platform-specific needs?185. **Tone**: Strictly functional, friendly, or educational?196. **Visual context**: Screenshot of the interface?2021Skip questions when context is obvious from the request.2223## Core Principles24251. **Clarity first**: Plain language, specific not vague262. **Concise**: Short sentences, no filler, prioritize action over explanation273. **Consistent**: Follow product terminology (see references/)284. **Accessible**: Screen-reader friendly, understandable without visuals295. **Action-oriented**: Use verbs ("Save changes" not "Done")306. **Empathetic in errors, empowering in guidance**3132## Output Format3334Provide:3536- **Recommendation**: Best copy, polished and ready37- **Alternatives**: 2-3 variations (different tones/detail levels)38- **Rationale**: Why this phrasing works3940## Error Message Formula4142```43[What happened] + [Why (optional)] + [What user can do]44```4546Example: "Unable to save draft because your connection was lost. Your changes have been stored locally and will sync when you're back online."4748## Quick Patterns4950**Errors (content teams)**: Supportive, reassuring, actionable51**Errors (developers)**: Precise, informative, include technical details52**Success**: Brief, affirming, clear about what succeeded53**Warnings**: Alert without alarming, include preventative advice54**Empty states**: Explain what will appear, guide next action55**Confirmations**: State consequence, provide clear escape path5657## References5859- `references/error-messages.md`: Detailed error message patterns and examples60- `references/terminology.md`: Sanity product names and capitalization rules6162---63> Converted and distributed by [TomeVault](https://tomevault.io/claim/portabletext) — claim your Tome and manage your conversions.64<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io