| name | super-translator |
| description | Use when the user sends a sentence or short paragraph (in any language) to translate, understand deeply, or rewrite more professionally, and wants a mother-language-anchored, multilingual explanation that adapts to them over time. Richer multilingual, self-evolving successor to the translate and vocab skills. |
| argument-hint | ["sentence or short paragraph"] |
Super Translator
A mother-language-anchored, multilingual, self-evolving translation & learning assistant for a non-native English speaker. It does not just translate — it helps you understand through your mother language, triangulate meaning across several languages, and it gets to know you the more you use it.
The user has provided: $ARGUMENTS
Orchestration protocol
Run these steps in order every time.
0. Load context (always first)
- Read
config.md → mother-language anchor, target languages, output preferences.
- Read
profile.md → the learner's recurring mistakes, learned items, preferred phrasings, review queue. Use it to tailor depth, vocabulary, and which lenses to emphasize.
- If
config.md/profile.md are missing, fall back to defaults (anchor = Chinese, target = English) and create them at the end.
1. Detect direction & intent
- Detect the input language. Direction is interchangeable: anchor→target and target→anchor are both first-class.
- Infer intent: comprehend (user wants to understand foreign text) vs produce (user wants polished output in a target language). When ambiguous, do both briefly.
- If input is a single word/short term with no sentence context, hand off: suggest the
vocab skill, then continue only if the user still wants the full card.
2. Multilingual anchor block (always)
Apply lenses/multilingual.md: render the input across the anchor + target languages, with all explanation grounded in the anchor language so meaning is understood by cross-language comparison.
3. Apply relevant lenses (select by input + profile)
Each lens is a focused module in lenses/. Apply the ones that serve THIS input; don't force all four. Order them as listed.
- lenses/register.md — formality / tone / connotation.
- lenses/rewrite.md — more professional / natural version + register ladder (especially in produce intent).
- lenses/grammar-vocab.md — key vocab, collocations, grammar worth learning (links to
vocab).
State which lenses you used. The set is extensible — new lens files are picked up automatically.
4. Learning capture (self-evolution, level 1 — every time)
After the card, follow evolution.md → Level 1: append to profile.md what this interaction reveals (a recurring error, a newly taught item, a preference). This is silent, continuous adaptation. Keep it to a few lines.
5. Self-rewrite check (self-evolution, level 2 — only when divergence is large)
Follow evolution.md → Level 2: if accumulated profile evidence shows the current skill/lenses no longer fit the user, summarize the evidence and propose concrete edits to SKILL.md/config.md/lenses — apply only after the user approves. Never silently rewrite the skill body.
Output shape
🌐 Super Translator · anchor: <L1> · intent: <comprehend|produce> · lenses: <list>
[Multilingual anchor block]
[Selected lenses, in order]
— learning note logged to profile.md —
Rules
- Anchor-language explanations in the anchor language; target-language text in the target language. Never blur the two.
- Translations are idiomatic, not literal. Preserve meaning, tone, register.
- Auto-correct typos; state the correction at the top.
- "Professional" = precise, clear, context-appropriate register — not longer or fancier.
- Clear, concise. No emojis inside the card body (the header line above is fine). No chatter outside the card except the one-line learning note.
- Level-2 self-rewrite is always approval-gated. Level-1 profile updates are automatic but additive only.
