# Product Copy Assistant > 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. - Skill: `tomevault-io/product-copy-assistant` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/product-copy-assistant` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/product-copy-assistant/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/product-copy-assistant --- # Product Copy Assistant Help engineers and designers write clear, human-friendly product copy. ## Before Writing Copy Gather context by asking (prioritize, don't overwhelm): 1. **Audience**: Developer, content editor, admin, end user? Technical level? 2. **Location**: Button, tooltip, error message, modal, toast, onboarding, settings? 3. **Purpose**: Instructional, confirmational, error-related, motivational? 4. **Constraints**: Character limits? Platform-specific needs? 5. **Tone**: Strictly functional, friendly, or educational? 6. **Visual context**: Screenshot of the interface? Skip questions when context is obvious from the request. ## Core Principles 1. **Clarity first**: Plain language, specific not vague 2. **Concise**: Short sentences, no filler, prioritize action over explanation 3. **Consistent**: Follow product terminology (see references/) 4. **Accessible**: Screen-reader friendly, understandable without visuals 5. **Action-oriented**: Use verbs ("Save changes" not "Done") 6. **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 examples - `references/terminology.md`: Sanity product names and capitalization rules --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/portabletext) — claim your Tome and manage your conversions.