agentleFS
forsvn-labsforsvn-labs/meta-skills/skills/polish-vietnamese/SKILL.md

polish-vietnamese

Skill14 starsChanged 3 months agoMITView on GitHub

Create, rewrite, translate, or edit Vietnamese marketing and product language so it sounds natural, precise, and appropriate to the audience. Use for Vietnamese copy, localization, tone and pronoun consistency, removing English calques, regional register, founder or company voice, and preserving factual claims while improving rhythm.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create natural Vietnamese, not English syntax with Vietnamese words.

    line 11
  2. Distinctive:

    Ask only when pronoun or register choices would materially alter the relationship.

    line 24
  3. Distinctive:

    Prefer active, spoken phrasing where the context allows it.

    line 30
  4. Distinctive:

    Keep common loanwords when the audience naturally uses them.

    line 31
  5. Distinctive:

    Remove filler transitions, redundant classifiers, formalism without purpose, and machine-like parallelism.

    line 35
  6. Distinctive:

    Avoid slang inventories, forced particles, theatrical intimacy, and mixed levels of formality.

    line 37
  7. Distinctive:

    Read the complete result aloud for pronoun drift, mixed formality, unnatural rhythm, accidental claim changes, punctuation, and …

    line 51
  8. Distinctive:

    Never invent facts, quotes, metrics, or consent while rewriting.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Polish Vietnamese language

Create natural Vietnamese, not English syntax with Vietnamese words.

Set the language contract

Infer or state:

  • audience and relationship;
  • conversational, professional, corporate, editorial, or other register;
  • sustainable self/reader pronoun pair;
  • regional preference when it materially affects vocabulary;
  • founder, company, product, or narrator voice;
  • facts, claims, numbers, product names, and legal language that must not change.

Ask only when pronoun or register choices would materially alter the relationship. Otherwise choose a reasonable default and state it briefly.

Rewrite for Vietnamese logic

  • Rebuild English noun stacks into clear Vietnamese clauses.
  • Prefer active, spoken phrasing where the context allows it.
  • Keep common loanwords when the audience naturally uses them.
  • Translate or explain terminology only when clarity improves.
  • Preserve claim strength; do not turn a possibility into a guarantee.
  • Preserve intentional technical precision, names, numbers, and source meaning.
  • Remove filler transitions, redundant classifiers, formalism without purpose, and machine-like parallelism.
  • Avoid slang inventories, forced particles, theatrical intimacy, and mixed levels of formality.

For translation, translate the communication job and social relationship, not the source sentence order. For editing, preserve the author's point of view and product-specific vocabulary.

Deliver

Return the finished Vietnamese first. When useful, add:

  • the chosen register and pronoun pair;
  • materially changed phrases and why;
  • ambiguous source claims or terminology needing confirmation;
  • alternate wording only when it represents a real register choice.

Read the complete result aloud for pronoun drift, mixed formality, unnatural rhythm, accidental claim changes, punctuation, and line-breaking. Do not explain every edit.

Never invent facts, quotes, metrics, or consent while rewriting. Keep sending, publishing, and external writes behind explicit approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.