UX Writing
Use when
Writing or revising interface copy, labels, validation, errors, empty states, onboarding, confirmations, or destructive-action messaging.
Procedure
- Identify the user's task, context, and consequence of misunderstanding.
- Match established product voice and terminology.
- Prefer concrete action language over vague system language.
- For errors, state what happened, what the user can do, and what data/state is preserved when relevant.
- For empty states, distinguish true zero-data states from loading, permission, filtering, and failure states.
- Make destructive actions explicit about scope and reversibility.
- Keep labels stable across UI, documentation, and validation.
- Check that text expansion/localization will not break the component contract where relevant.
Failure conditions
Do not use copy to hide missing product behavior. A message saying an action succeeded is a defect if the underlying state did not change.
1---2name: ux-writing3description: UX Writing4---5# UX Writing67## Use when89Writing or revising interface copy, labels, validation, errors, empty states, onboarding, confirmations, or destructive-action messaging.1011## Procedure12131. Identify the user's task, context, and consequence of misunderstanding.142. Match established product voice and terminology.153. Prefer concrete action language over vague system language.164. For errors, state what happened, what the user can do, and what data/state is preserved when relevant.175. For empty states, distinguish true zero-data states from loading, permission, filtering, and failure states.186. Make destructive actions explicit about scope and reversibility.197. Keep labels stable across UI, documentation, and validation.208. Check that text expansion/localization will not break the component contract where relevant.2122## Failure conditions2324Do not use copy to hide missing product behavior. A message saying an action succeeded is a defect if the underlying state did not change.
devotionn