Textos de interfaz claros

Screen: Sign up
1. Button: Click here to submit your registration form
2. Error (email field): Invalid email
3. Error (password field): Password does not meet requirements
Screen: Projects list
4. Empty state: No data
5. Button: Proceed to checkout page
Screen: Account settings
6. Link: Login / Sign in / Log-in (used in different places)
7. Button: Cancel Subscription Now!!
8. Toast after saving: Your changes have been successfully saved!
Screen: Upload
9. Error: Upload failed due to file size
10. Button on delete dialog: OK
11. Dialog text: Are you sure you want to delete this?
Screen: Notifications
12. Empty state: You have no notifications at this time.

# UX copy review: 12 strings
9 rewritten, 3 kept as they are until you add product context (#3, #10, #11). #9 is rewritten but also needs one fact.

## Before / after
| # | Screen | Before | After | Words | Reason |
|---|---|---|---|---|---|
| 1 | Sign up | Click here to submit your registration form | Register | 1 | Verb first, removes filler. |
| 2 | Sign up | Invalid email | Enter an email like name@example.com | 5 | Tells the user what to do. |
| 4 | Projects list | No data | No projects yet. Create your first project. | 7 | Says what is missing and the next action. |
| 5 | Projects list | Proceed to checkout page | Go to checkout | 3 | Shorter, same meaning. |
| 6 | Account settings | Login / Sign in / Log-in | Log in | 2 | One term everywhere. |
| 7 | Account settings | Cancel Subscription Now!! | Cancel subscription | 2 | No shouting, no exclamation marks. |
| 8 | Account settings | Your changes have been successfully saved! | Changes saved | 2 | States what happened in two words. |
| 9 | Upload | Upload failed due to file size | File is too big. Choose a smaller file. | 8 | Says what to do; the limit is not known, see context list. |
| 12 | Notifications | You have no notifications at this time. | No notifications yet | 3 | Shorter, friendlier. |

## Terms chosen
- Log in (verb), not Login, Sign in or Log-in.
- Buttons start with a verb. Messages avoid please and exclamation marks.

## Needs product context
- #3 Password does not meet requirements: list the actual password rules so the error can show them.
- #9 Upload failed due to file size: give the maximum size so the error can name it.
- #10 OK (delete dialog): needs the action name, for example Delete or Keep.
- #11 Are you sure you want to delete this?: needs the item name and whether delete can be undone.

---
name: ux-copy-fixer
description: Rewrites interface texts (buttons, errors, empty states, toasts) into clear, short, consistent microcopy, with a before/after/reason table and a list of strings that need product context. Use when someone pastes UI strings to tidy up before a release or design review.
---
# UX Copy Fixer
Messy interface strings in, short consistent copy out, with the reason for every change.

## When to use
- The user pastes buttons, error messages, empty states or toasts to improve.
- The user wants one consistent voice and vocabulary across screens.

## Inputs
- The strings, ideally with the screen or element for each. Ask where a string appears if it is unclear.
- Optional: product name, audience, tone, a glossary of preferred terms.

## Steps
1. Number every string and note its type: button, link, error, empty state, toast, dialog.
2. Find inconsistent terms (for example Login / Sign in / Log-in) and choose one form for the whole set. Use the glossary if given.
3. Rewrite by type:
   - Buttons and links start with a verb and say what happens: "Create account".
   - Errors say what to do next, in a calm tone, no blame, no codes.
   - Empty states say what is missing and offer the next action.
   - Toasts are short statements of what happened.
   - Remove "please", exclamation marks, capital-letter shouting and filler words.
4. Check every new string: at most 12 words (count with code), same term for the same thing.
5. If a rewrite needs a fact you do not have (a limit, a rule, what a dialog deletes), keep the original and add it to the context list. Do not guess.
6. Write one short reason for each change.

## Output
Write a new file `ux-copy.md` next to the input (if it exists, use `ux-copy-2.md`). Never overwrite the input. Template:
```
# UX copy review: <n> strings
## Before / after
| # | Screen | Before | After | Words | Reason |
## Terms chosen
## Needs product context
- #<n> <string>: what is missing
```

## Rules
- Never invent product facts, limits, rules, features or consequences; unknown details go to the context list.
- Keep the meaning of the original; do not change what an action does.
- Use the same word for the same thing everywhere.
- Mark rewrites that depend on an assumption.
- Write results to a new file, never overwrite the user's files.
- Keep the strings local; do not send them anywhere.
- Out of scope: legal wording such as consent or terms text; flag it for a professional.