Menu
Propagate new player-facing text through DOTS's 12-language localization pipeline — wrap with {=KEY}, register the string, run the Claude translation tool, validate. Use after adding UI text or XSLT strings.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | localize |
| description | Propagate new player-facing text through DOTS's 12-language localization pipeline — wrap with {=KEY}, register the string, run the Claude translation tool, validate. Use after adding UI text or XSLT strings. |
| argument-hint | ["c#|xml-file|xslt"] |
Get new player-facing text into all 12 supported languages (BR, CNs, CNt, DE, FR, IT, JP, KO, PL, RU, SP, TR). Full reference: docs/localization/TRANSLATOR_GUIDE.md + tools/README.md (localization section). Three cases:
new TextObject("{=dots_my_feature_label}My Feature") (always {=KEY}default form).Main/_Module/ModuleData/dots_module_strings.xml.python tools/translate_with_claude.py (machine-translates to the 11 AI languages; PL is hand-translated, overrides in tools/translation_overrides/<lang>.json always win).SubModule.xml as <XmlNode><XmlName id="GameText" path="..."/>.<LanguageFile> reference in all 12 language_data.xml files.Languages/<LANG>/std_dots_*.xml).LanguageDataXmlTests.HaveExactlyXLanguageFiles count in DOTS.Tests/Infrastructure/Localization/LanguageDataXmlTests.cs.tools/translate_with_claude.py.{=KEY}default textMain/_Module/ModuleData/dots_xslt_strings.xml (precedent: commit 20713a1).tools/translate_with_claude.py.tools/translate_with_claude.py — 4-tier fallback (override → cache → Claude LLM → English); cache in tools/translation_cache/<lang>.json is git-tracked, so re-runs are free.tools/rebuild_translation_files.py — rebuild per-language files from cache.tools/translation_status.sh — coverage report.dotnet test DOTS.Tests --filter "LanguageDataXmlTests" — enforces 7 LanguageFile refs/language, well-formed XML, no missing files. For Case B the test count bump is mandatory or this goes red.
DOTS_Map, LOTRLOME_Armory) deployed straight to the game install — not in the repo.Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules.
Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Author or revamp a DOTS culture's armor set, troop tree, and recruitment wiring end-to-end. Use for new cultures or troop-tree revamps. Follows docs/ai-includes/new-culture-authoring.md.
Use when reviewing an external repo or article to adopt practices into DOTS — security-vet first, map novel vs duplicative, port (never install), review, commit your changes.
Structured 4-phase self-debug for failing agent runs (looping, drifting, burning tokens). Capture, diagnose, contained recovery, report. Complements /investigate (which is for code bugs); this skill is for harness/agent failures.
Incrementally fix dotnet build errors with minimal diffs, one error at a time