agentleFS
Sign inStart free
marticlimentmarticliment/UniGetUI/.agents/skills/translation-diff-translate/SKILL.md

translation-diff-translate

Skill27k starsChanged 6 months agoMITView on GitHub

Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back. Use when the user asks to translate or localize i18n strings, localization JSON, or language-file patches.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill after translation-diff-export produced a .source.json, .translated.json, and .reference.json set and you want to update the …

    line 8
  2. Distinctive:

    Do not install packages or search for external translation services unless the user explicitly asks for automation.

    line 15
  3. Very specific:

    If .translated.json is empty, that is expected.

    line 16
  4. Very specific:

    Use .reference.json only as terminology guidance, not as a reason to pause and analyze the rest of the repository.

    line 17
  5. Distinctive:

    If the patch is too large to finish reasonably in one pass, report that constraint to the user instead of creating automation on your own.

    line 18
  6. Very specific:

    Do not edit .source.json.

    line 44
  7. Very specific:

    Write completed translations only into .translated.json.

    line 45
  8. Very specific:

    If a key is not translated yet, omit it from .translated.json instead of copying the English source value.

    line 46
  9. Very specific:

    Keep translated entries in the same key order as .source.json when adding new entries.

    line 49
  10. Very specific:

    Use .reference.json to match existing terminology and tone in the destination language.

    line 50
  11. Distinctive:

    Do not introduce keys that are not present in the source patch.

    line 51

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

translation diff translate

Use this skill after translation-diff-export produced a .source.json, .translated.json, and .reference.json set and you want to update the sparse translated working copy.

It translates only the active patch keys, keeps .translated.json as the sole writable file, preserves placeholders and formatting, and hands the completed working copy to translation-diff-import for merge-back.

Execution Expectations

  1. Edit .translated.json directly. Do not create helper scripts, temporary reports, or coverage probes.
  2. Do not install packages or search for external translation services unless the user explicitly asks for automation.
  3. If .translated.json is empty, that is expected. Translate from .source.json into .translated.json.
  4. Use .reference.json only as terminology guidance, not as a reason to pause and analyze the rest of the repository.
  5. If the patch is too large to finish reasonably in one pass, report that constraint to the user instead of creating automation on your own.

Script

  • scripts/write-translation-handoff.ps1: Writes a small .prompt.md file that points an agent at this skill with the concrete patch paths created by the export skill.

Usage

Generate a handoff prompt for a translated French working copy:

pwsh ./.agents/skills/translation-diff-translate/scripts/write-translation-handoff.ps1 \
  -BaseName lang \
  -Language fr \
  -SourcePatch ./generated/translation-diff-export/lang.diff.fr.source.json \
  -TranslatedPatch ./generated/translation-diff-export/lang.diff.fr.translated.json \
  -ReferencePatch ./generated/translation-diff-export/lang.diff.fr.reference.json \
  -TargetJson ./src/Languages/lang_fr.json \
  -NeutralJson ./src/Languages/lang_en.json \
  -MergedTargetJson ./src/Languages/lang_fr.merged.json \
  -ValidationScript ./.agents/skills/translation-diff-import/scripts/validate-language-file.ps1 \
  -OutputPrompt ./generated/translation-diff-export/lang.diff.fr.prompt.md

Translation Rules

  1. Do not edit .source.json.
  2. Write completed translations only into .translated.json.
  3. If a key is not translated yet, omit it from .translated.json instead of copying the English source value.
  4. Preserve key names exactly as-is.
  5. Preserve placeholders, named tokens, HTML-like fragments, escape sequences, and line breaks.
  6. Keep translated entries in the same key order as .source.json when adding new entries.
  7. Use .reference.json to match existing terminology and tone in the destination language.
  8. Do not introduce keys that are not present in the source patch.

After Translation

Merge the sparse working copy back into the full destination-language file:

pwsh ./.agents/skills/translation-diff-import/scripts/import-translation-diff.ps1 \
  -TranslatedPatch ./generated/translation-diff-export/lang.diff.fr.translated.json \
  -SourcePatch ./generated/translation-diff-export/lang.diff.fr.source.json \
  -TargetJson ./src/Languages/lang_fr.json \
  -NeutralJson ./src/Languages/lang_en.json \
  -OutputJson ./src/Languages/lang_fr.merged.json

pwsh ./.agents/skills/translation-diff-import/scripts/validate-language-file.ps1 \
  -NeutralJson ./src/Languages/lang_en.json \
  -TargetJson ./src/Languages/lang_fr.merged.json \
  -PatchJson ./generated/translation-diff-export/lang.diff.fr.source.json

Download now (ZIP)

Trending

Quiet since May.about the whole repository

Dec 2025: 0 mentionsJan 2026: 4 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the marticliment/UniGetUI repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about marticliment/UniGetUI

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on YouTube, GitHub and Bluesky (52 times).

On YouTube · 25

20 more on YouTube

On GitHub · 18

13 more on GitHub

On Bluesky · 9

4 more on Bluesky
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Devolutions/UniGetUI★ 27k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

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.

Check your setup, free