cami-design-copylisted

# Cami — Copy ## Required reading Before proceeding, load `../cami-design/references/review-protocol.md` for the shared **Context Gathering Protocol**, **Design System Protocol**, severity scale, and **Review Output Format**. For copy work you also need: - **Voice / tone**: how does the product speak? (formal, friendly, sharp, playful, neutral) - **Audience literacy**: technical users? consumers? mixed? - **User's mental state in context**: stressed during errors? confident during success? anxious during payment? Copy should match the emotional register of the moment. If the audited surface includes form controls, also load `../cami-design/references/forms.md` — labels, placeholders, error placement, confirmations, and unsaved-changes warnings are all canonicalised there. --- Improve the words users read. Clearer labels, kinder errors, useful empty states, a tone that matches the brand. ## When to Use This Mode - Labels are ambiguous or jargon-heavy - Error messages blame the user or say nothing actionable - Empty states are blank or unhelpful - CTAs don't tell the user what happens next - Tone drifts across the product - User says "this text is confusing" ## Review Dimensions ### Clarity - Every label tells the user what will happen, in their words - No jargon unless the audience uses it naturally - One idea per sentence - Prefer active voice: "We uploaded your file" not "Your file has been uploaded" ### Actionability (especially errors) - Error messages say: what