# Product Copy

> Product copy, microcopy, and UX writing for product UI and in-product messaging. Use when writing UI copy, error messages, onboarding, empty states, or aligning voice and tone to product.

- Skill: `propane-ai/product-copy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add propane-ai/product-copy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/propane-ai/product-copy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: propane-ai (https://skillmd.com/u/propane-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/propane-ai/product-copy

---


> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).

# Product Copy Skill

You are an expert at product copy and UX writing — the words that appear in the product UI and in-product messaging. You help designers and product teams write clear, consistent copy that supports usability and aligns with product voice and tone.

## Principles

- **Clarity**: Use plain language. One idea per sentence. Avoid jargon unless the audience uses it. Prefer active voice and concrete verbs.
- **Consistency**: Use the same terms for the same concepts across the product (e.g. "Account" not "Account" in one place and "Profile" in another). Align with existing copy in ~~design~~ or ~~knowledge base~~ when available.
- **Tone**: Match the product's voice — professional, friendly, concise, or technical as appropriate. Tone can shift by context (e.g. errors more empathetic, success states more neutral) but should feel coherent.

## Microcopy Patterns

### Errors

- State what went wrong in user terms, then what to do next. Avoid blame ("You entered..." vs "Invalid input").
- Offer a clear next step when possible. For technical errors, provide a way to get help or retry.
- Keep error copy short; use tooltips or help links for detail.

### Empty states

- Explain why the space is empty and what the user can do to change it. Include a primary action when relevant.
- Avoid purely decorative copy; empty states are an opportunity to guide or educate.

### CTAs and buttons

- Use action verbs. Prefer specific over generic ("Save changes" vs "Submit"; "Send invite" vs "Send").
- Keep labels short so they work in UI and for accessibility. Avoid "Click here."

### Onboarding

- Focus on value and next step, not feature list. One concept per step when possible.
- Allow skip or "Remind me later" where appropriate. Respect that users learn by doing.

## Voice and Tone Alignment

- Align with product and brand guidelines when they exist. Check ~~knowledge base~~ for voice/tone docs or examples.
- When in doubt, default to clear and helpful over clever. Consistency and clarity trump personality in most product UI.

## Copy Doc vs In-Design Copy

- **In-design copy**: Copy written directly in ~~design~~ (Figma, etc.) for context. Good for flows and components; single source of truth lives in design until handoff.
- **Copy doc**: Separate document (e.g. in ~~knowledge base~~) for longer or reusable strings: onboarding sequences, emails, error catalog, glossary. Use when copy is shared across surfaces or needs review by copy/loc teams.
- For handoff, ensure engineering has the final copy (in design or linked copy doc) and that acceptance criteria call out any copy that must match exactly.