# UI Copywriting — Derived Rules

> Derives from `domains/uiux/first-principles.md` P3 (Clarity), P1 (User Primacy), P5 (Forgiveness).

## Write for the User (P1 User Primacy)

- The reader is a user, not a developer. "Sign in" not "Authenticate."
- The reader is busy. Short sentences. Active voice. Verbs first.
- The reader is anxious. Reassure. "Your changes are saved." Not "State persisted."

## Clarity (P3)

- One idea per sentence. One action per button.
- Labels are nouns: "Email", "Password". Actions are verbs: "Sign in", "Save".
- Errors are specific: "Email is invalid" not "Something went wrong."
- Empty states are instructive: "No projects yet. Create one." Not "No data."

## Forgiveness (P5)

- Destructive actions warn: "This will delete 42 items. This cannot be undone."
- Confirmations name the consequence, not just the action. "Delete user" → "Delete Jane Doe and 12 associated items?"
- Undo is offered when possible. "Deleted. Undo." beats "Are you sure?" when undo is cheap.

## Tone (P3, P1)

- Helpful, not clever. Cleverness ages. Helpfulness does not.
- Apologetic when the system is at fault. "We couldn't save that. Try again." Not "Error."
- Neutral, not excited. "Saved." Not "Awesome! Saved!! 🎉" (unless the brand is intentionally playful).

## Microcopy (P3 Clarity, P9 Simplicity)

- Buttons: 1–3 words. "Sign in", "Create account", "Send invite".
- Tooltips: 1 sentence. Explain what the field does, not what the label says.
- Empty states: 1 sentence of explanation + 1 action. "No team members yet. Invite your first."
- Loading: present tense. "Saving..." not "Saved" (until it is).

## What Violates UI Copywriting

| Violation | Principle |
|-----------|-----------|
| "Error code 500" to a user | P3, P1 |
| "Are you sure?" with no consequence | P5 (no information) |
| "Submit" on a delete button | P3 (wrong verb) |
| 50-word tooltip | P9 Simplicity |
| "Awesome!" on a routine save | P1 (not for the user) |