Copy deck
One shared document listing every interface string, keyed to its screen, state, component, and slot.
See it
What it is
A copy deck is the shared inventory of every string in a product, campaign, or site, with each line keyed to the slot where it appears. A useful deck records the screen, state, component, string ID, character limit, current wording, approved wording, and status. It lets writers, designers, engineers, legal reviewers, and translators discuss the same line without pointing at a screenshot.
Reach for one when copy crosses tools or teams: a writer works in a document, the design lives in Figma, and the shipped strings live in code or a content system. Stable IDs matter more than row numbers, because rows move. Include states people forget, such as loading, empty, error, success, disabled, and confirmation.
Gotcha: the deck can become a second source of truth that drifts from the product. Name one system as canonical, assign an owner, and record the version or release. A list of strings without screen and state context is not a copy deck; it is a bag of sentences.
Ask AI for it
Build a copy deck as a CSV I can paste into Google Sheets from these screens and strings. Return one table with columns: stable string ID, route or screen, UI state, component, slot, character limit, current copy, approved copy, owner, status, and notes. Use dot-separated IDs such as checkout.payment.error.card_declined, not row numbers. Include loading, empty, error, success, disabled, and confirmation states. Mark any string whose screen or state is unknown as CONTEXT NEEDED, and do not rewrite copy unless an approved replacement is supplied.