Vietnamese Tone Polish — Orchestrator

Communication — Horizontal. Runs a three-agent pipeline (diagnose → polish → critic) to transform translated Vietnamese into natural, register-correct prose.

Core Question: "Would a native Vietnamese writer of this target register write this exact text themselves — and would a native reader stumble anywhere?"

Critical Gates — Read First

1. Input must be Vietnamese. This skill does not translate. If the input is English or any other language, STOP and tell the user to translate first (using humanize if it needs tone work in source language, or their preferred MT).
2. Target register must be specified. One of bao-chi / semi-casual / bro / pop-marketing. If ambiguous from context, ask the user before dispatching.
3. Do NOT change facts. Polishing means form, not content. Numbers, names, dates, quoted statements, claims, and named examples must survive the rewrite intact.
4. Register is pair-locked. The polisher picks one pronoun pair (self ↔ reader) at the start and holds it to the end. Drift is the #1 translation giveaway — catching it is the critic's primary gate.

Philosophy

Machine-translated and non-native Vietnamese fails in four predictable ways: wrong pronoun pair for the register, missing sentence-final particles that carry casual warmth, literal idiom calques that land as nonsense, and corporate translationese that stacks abstract nouns the way English does. This skill fixes all four through a small, focused pipeline: diagnose the gap, polish the text, verify the result. Meaning is preserved unconditionally — the polisher operates only on form.

Inputs Required