通过填写源语言、目标语言与地区、语域、受众、内容类型等字段，让模型在翻译时保留语气和意图，而不是逐词替换。

Translate the text below. SOURCE LANGUAGE: [English / auto-detect and tell me what you detected] TARGET LANGUAGE + LOCALE: [Spanish (es-MX) / German (de-CH) / Japanese (ja-JP)] REGISTER: [name the exact form, not "formal" — see the table below] e.g. Spanish: use "tú" throughout, never "usted" e.g. German: use "du" throughout, never "Sie" e.g. Japanese: teineigo (です/ます). No sonkeigo, no kenjougo, no plain form. AUDIENCE: [existing paying customers, 25-40, already know the product] CONTENT TYPE: [in-app error / landing page / support email / UI button label / legal summary / social post] TONE: [warm, direct, slightly apologetic. Short sentences.] INTENT: [what the reader should do or feel after reading — they retry the action, they do not feel blamed] DO NOT TRANSLATE (reproduce exactly, including case and punctuation): [Prompt Architects, Enhance, Refine, Pro, Advanced, {user_name}, %s, <b>, </b>] LENGTH CONSTRAINT: [must fit a 24-character button / within ±15% of the source / no constraint] OUTPUT FORMAT: [translation only, nothing else / table: source | translation | note] RULES: - Translate meaning and intent, not words. Reword freely if a literal rendering would sound translated. - Hold the register identical in every sentence. Do not drift formal mid-text. - Where the source is ambiguous, choose the reading that fits AUDIENCE and CONTENT TYPE, then flag it under NOTES. - Do not add, remove or soften any claim, number, date, name or obligation. - Idioms: replace with a native idiom of equal force, never a literal calque. List every swap under NOTES. - If a DO NOT TRANSLATE term has an established local form, leave the source form and say so under NOTES. Do not decide that on your own. - End with NOTES: at most 5 bullets. Ambiguities, register calls, idiom swaps. TEXT: [paste here]