Bilingual Output That Stays Parallel

What it is for

Ask for two languages and the second usually drifts into a loose paraphrase of the first. This keeps them parallel — same claims, same order, same numbers — which is what makes bilingual output usable rather than decorative.

The skill Copy

Ask for both languages in one pass, structured, and constrain the relationship
between them.

    For each item output exactly:
      EN: <the English>
      XX: <the other language>
    Same number of items. Same order. Same meaning, not the same words.

Rules that stop the usual failure:
- **Translate the MEANING, match the REGISTER.** A formal English sentence
  becomes a formal sentence in the target, not a literal word map.
- **Numbers, product names, code and URLs are copied, never translated or
  re-scripted.** This is the rule most often broken, and it silently corrupts
  a price list or an API key.
- **Do not add.** If the second language needs a clarification the first did
  not, that is a sign the first was ambiguous — fix the source instead.
- For Persian and Arabic, ask explicitly for the correct half-space / letter
  forms; a model producing Arabic yeh in Persian text is the commonest tell.

Verify by asking for the reverse translation of the second column only, and
comparing it to the first. Drift shows up immediately.

How to install it Copy

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from