microcopylisted

# Microcopy ## Coverage Functional UI text patterns across all interactive surfaces: - **Button labels** — verb-first, specific action, max 3 words; never generic ("Submit", "OK", "Yes", "Continue") - **Empty states** — three-part structure: acknowledge → explain → guide, with one primary action - **Tooltips** — one sentence, no terminal period, answers "what is this?" - **Confirmation dialogs** — state the consequence first, name the action in the button, always provide an escape - **Placeholder text** — example format not instruction; never the only label for a field - **Loading and progress messages** — progressive disclosure: nothing → spinner → skeleton → message → reassurance, by elapsed time - **Error / success / warning messages** — three-part What → Why → What-to-do structure with blame-free framing - **Inline form-validation messages** — appear on blur, disappear on fix, specific not generic - **Toast / snackbar messages** — action plus context, undo for reversible actions, auto-dismiss after 5 seconds, max 2 lines - **Permission request copy** — explain *why* before asking - **Onboarding step copy** — one action per step, progressive disclosure, time-honest ## Philosophy Microcopy is the most-read, least-reviewed text in any application. A user may never read the docs, skip the onboarding, and ignore the marketing — but they will read the button label before clicking it. They will read the error message when something fails. They will read the empty state when