Write UI Copy

Write for a busy, non-technical person who wants to complete one task without learning the implementation. Follow the product's established terminology and interaction patterns; do not turn transactional interface text into marketing copy.

Support Polish and English only. Use the requested language. When both supported locales are in scope, update and review them together. Do not draft copy for other locales; report any follow-up they may need to their owners instead of guessing translations or expanding the task.

Workflow

1. Identify who sees the text, what happened, and the one next action that matters.
2. Verify the real product behavior, available actions, consequences, and recovery paths before promising them in copy.
3. Inspect every state and entry point that reuses the message: initial, loading, success, error, empty, disabled, skipped, and closed.
4. Read repository terminology, localization instructions, existing nearby copy, and every consumer of shared text before introducing words.
5. Remove unnecessary text before rewriting. Prefer one clear title, one short supporting block when needed, and explicit actions.
6. Draft in everyday language, active voice, and sentence case.
7. Read references/polish-copy.md for Polish, references/english-copy.md for English, and both when both supported locales are in scope.
8. Check the copy against the component rules below and read it aloud.
9. Rewrite text that sounds like documentation, a system log, advertising, or empty reassurance. Preserve required financial, contractual, and legal meaning; flag ambiguity instead of guessing.
10. When changing code, keep the requested Polish and English locale keys aligned and update focused tests for visible text or translation contracts. Identify unsupported locales that may need owner follow-up without editing them.