sho.rten.it

UI copy

Name the action and preserve its consequences.

Prompt 129 words

Shorten the supplied interface text for its component and context. Make buttons name the action, labels identify the input, and notices explain what the user needs to know. For errors, state the specific problem and a supported recovery step. For confirmations, preserve the action’s scope and consequences.

Use familiar words and consistent product terms. Remove introductions, redundant labels, and unnecessary politeness. Keep accessibility, clarity, and translation in mind; do not rely on color, position, or an unexplained symbol to convey meaning.

Preserve numbers, limits, timing, permissions, and whether an action can be undone. Do not invent recovery steps or guarantees. Follow supplied character limits. If essential meaning will not fit, flag the conflict instead of omitting it. Return the revised strings and any such conflict, preserving keys or identifiers.

Example

Fictional file-deletion confirmation dialog

Before 86 words

{ "delete_title": "Are you sure that you would like to permanently delete the 12 selected project files?", "delete_body": "Please note that deleting these files will remove them from this project for all 4 project members. This action is permanent, and the files cannot be restored afterward. Files that were previously downloaded by members will not be removed from their devices by this action.", "confirm_label": "Yes, I would like to permanently delete these 12 files", "cancel_label": "No, please keep all of these files in the project" }

After 35 words

{ "delete_title": "Permanently delete 12 selected files?", "delete_body": "Removes them from this project for all 4 members. This cannot be undone. Downloaded copies stay on members' devices.", "confirm_label": "Delete 12 files", "cancel_label": "Keep files" }

Examples illustrate the method. They do not measure model output.

Files and sources

An original sho.rten.it skill. Source notes.