OpenTagViewer: Skill for Claude Code

Adding user-facing strings

The app ships ten locales. A string missing from one silently falls back to English — nothing fails, and it looks correct in whichever language you happen to read. So every UI string has to land in every locale in one go.

The rule that matters

Never pass translations through a shell argument. Write a JSON file with the Write tool, then point the script at it. Passing non-ASCII text through bash -c, sed or a here-doc has corrupted it twice in this repo — a French apostrophe reached the screen as a literal \’. The Write tool does not go through shell quoting; a for loop does.

For the same reason, do not hand-edit ten strings.xml files with ten Edit calls unless the script cannot do what you need. It is slower and it is what the script exists to replace.

Workflow

1. Find out which locales are required — do not assume, they are discovered from the tree:

   python scripts/add_strings.py --locales
   

2. Write the JSON with the Write tool, one entry per string, every locale present:

   {
     "how_do_i_get_the_zip": {
       "default": "How do I get the zip?",
       "en": "How do I get the zip?",
       "de": "Wie erhalte ich die ZIP-Datei?",
       "fr": "Comment obtenir l’archive zip ?",
       "nl": "Hoe kom ik aan de zip?",
       "ru": "Как получить zip-архив?",
       "ja": "zip ファイルの入手方法",
       "ko": "zip 파일은 어떻게 받나요?",
       "zh-rCN": "如何获取 zip 文件？",
       "zh-rTW": "如何取得 zip 檔案？"
     }
   }
   

   Put it in the scratchpad or tmp/, not in the repo root.

3. Apply, then confirm nothing drifted:

   python scripts/add_strings.py tmp/new_strings.json
   python scripts/add_strings.py --check
   

4. Build. aapt is the real judge of whether the XML is acceptable:

   JAVA_HOME='C:\Program Files\Android\Android Studio\jbr' ./gradlew.bat :app:assembleDebug
   

Flags