---
name: copy-dock
description: Write and check product copy with your team's house style from Copy Dock. Use whenever you write, rewrite or review words people read in a product, such as button labels, error messages, empty states, onboarding, notifications, emails, tooltips, form labels and marketing lines, including text you put in code, Figma frames or string files.
---

# Copy Dock

Copy Dock holds your team's house style: voice rules, the word list (words to use and words to avoid), banned words, approved examples and product facts. It writes copy in that style and checks it. These instructions tell you when to use it. The rules themselves always come from Copy Dock, never from this file, so they stay current when the team changes them.

## Before you start

You need Copy Dock's connector. Its tools are `get_house_style`, `write_copy`, `check_copy`, `find_approved_copy`, `save_for_review` and `list_copy_types`.

If they aren't available, stop and tell the person: "Connect Copy Dock first: open copydock.design, go to Account, then Connected tools, and choose Connect a tool." Don't write copy from memory instead, and don't make up house rules.

## How to work

1. **Read the house style once per task.** Call `get_house_style`, naming the product if you know it. Keep its rules in mind for everything you write in the task.
2. **Reuse before you write.** For a common moment (a save button, a payment error, an empty list), call `find_approved_copy` first. If the team already approved wording for it, use that wording.
3. **Write new copy with `write_copy`.** Describe the moment in a sentence: what's happening, who it's for and what they should do next. Name the kind of copy (`list_copy_types` shows them all, such as "Button / CTA label" or "Error message") and pass the character limit when there is one. Offer the person the options it returns, not your own rewrite of them.
4. **Check copy you wrote yourself with `check_copy`.** This includes every user-facing string you add or change in code, a Figma frame or a strings file. When a string replaces copy that already ships, pass the old text as `shipped_text` so variable changes get caught. For product screens, pass `copy_kind: "ux"`; for marketing copy, decks and documents leave it out, so numbers and big claims are checked against the product facts.
5. **Act on the checks.**
   - A failed length or banned-words check means the copy can't ship. Fix it and check again.
   - Word list, spelling, reading level and placeholder warnings: fix them, or tell the person why you left them.
   - A facts warning means a number or claim isn't in the product facts. Remove it, or ask the person to confirm it and add it to their facts in Copy Dock.
   - Never hide a failed check. Show what failed and what you changed.
6. **Send finished copy for review.** When the person is happy with a piece of copy, offer to call `save_for_review`, so it joins the team's review queue with a key developers can use. Only save when they agree.

## Don'ts

- Don't override the house style with your own taste, even if you'd phrase something differently.
- Don't invent product facts, prices, limits or legal claims. If Copy Dock has no fact you need, leave a clear placeholder like [PRICE] and say so.
- Don't change copy that's already approved without saying it was approved and asking first.
