UX writing
Write interface language from the product job, evidence, anxiety, and vocabulary instead of a generic tone prompt.
What does the person need to understand or do next?
A narrow job with a visible boundary
Use it for labels, errors, confirmations, empty states, settings, and any string that carries part of the interaction.
Input
The interface state, the intended action, and relevant evidence or product terminology.
Outputs
- State-specific interface copy
- Evidence references beside decisions
- Alternatives for unresolved voice choices
Boundary
UX writing does not invent customer language. If evidence is absent, the wording remains a labeled hypothesis.
Invocation
humane:ux-writing
See the decision change
The upload stopped before the file was saved. Try again, or keep the file on this device.
The message names the state, consequence, and recovery.
1 / 2- Generic error
Oops! Something went wrong.
The upload stopped before the file was saved. Try again, or keep the file on this device.
- Empty state
No data.
No interviews yet. Add a transcript to start finding repeated jobs and language.
Run the skill by name
Install the Humane pack once, then name this skill when the task reaches its boundary.
humane:ux-writing