agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/locale-adaptation/SKILL.md

locale-adaptation

Skill220 starsChanged 20 days agoMITView on GitHub

Use when content must be rewritten for a specific region or language while preserving intent and tone—adapt idiom, dialect, register, cultural references, and protected glossary terms; flag meanings that cannot transfer cleanly. Not for literal word-for-word translation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read the source intent and tone before translating a word.

    line 12
  2. Distinctive:

    If a source claim or campaign cannot carry over without changing its meaning, surface options to the operator rather than silently altering …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Locale Adaptation

Adapt content for a target locale by meaning and tone — idiom, dialect, register, cultural fit — not literal translation.

Steps

  1. Read the source intent and tone before translating a word.
  2. Adapt idiom, register, and cultural references to the target locale; preserve meaning over literal wording.
  3. Annotate every place a literal rendering would mislead or offend.
  4. Honor the glossary / do-not-translate list supplied with the task; when none is supplied, extract the candidate terms and confirm them before translating.
  5. If a source claim or campaign cannot carry over without changing its meaning, surface options to the operator rather than silently altering it.

Acceptance

  • Meaning and tone are preserved; cultural mismatches are annotated.
  • Glossary and do-not-translate terms are respected.
  • Back-translation is used only as a diagnostic, never as proof of correctness.

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.