adding-localizable-strings
Adds new human-readable strings that are translated into users' languages.
Best use case
adding-localizable-strings is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Adds new human-readable strings that are translated into users' languages.
Teams using adding-localizable-strings should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adding-localizable-strings/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adding-localizable-strings Compares
| Feature / Agent | adding-localizable-strings | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Adds new human-readable strings that are translated into users' languages.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Adding Localizable Strings
## Instructions
Copy this checklist and check off items as you complete them.
```
Task Progress:
- [ ] Add the strings to the English strings file.
- [ ] Run `yarn translate` to translate to other languages.
- [ ] Run the full test suite with `./gradlew test`.
```
### Step 1: Add the strings to the English strings file
You will usually want to add strings to `src/main/resources/i18n/Messages_en.properties`.
Each string may be preceded with a comment line (starting with `#`). The comment is provided to the translation service and can provide additional context about the string to help produce grammatically-correct translations. This is optional and doesn't need to be provided if the English string is a simple, unambiguous word or phrase.
Add strings in alphabetical order by key. But don't insert a string in between a comment line and the existing string the comment is about. For example, if you see
stringX=Foo
# Comment for string Z
stringZ=Bar
and you are adding `stringY`, put it above string Z's comment, like
stringX=Foo
stringY=Why
# Comment for string Z
stringZ=Bar
Placeholders should be numbered starting with 0, enclosed in curly braces, like `{0}`.
Strings are rendered using Java's `MessageFormat`, which treats single quote characters (`'`) as special. If the English text contains single quotes, you must escape them by doubling them. For example, the word "can't" would need to be `can''t` in the file.
Stick to ASCII characters for punctuation.
### Step 2: Run "yarn translate" to translate to other languages
Only add strings to the English strings file. The strings files for other languages include metadata that you won't be able to generate yourself.
We have an automated translation tool that updates the files for other languages, including adding the right metadata.
Run `yarn translate` to update the non-English strings files with translations for newly-added and modified English strings.
### Step 3: Run the test suite
There are various tests that do sanity checking of the strings files. Run the full test suite to make sure you catch any problems.
If you're adding strings as part of a larger task, there's no need to run the full test suite multiple times; you can wait until you're done with the larger task.Related Skills
adding-tweets
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
adding-todos
Use this skill to capture an idea, task, or issue that surfaces during a Kata session as a structured todo for later work. This skill creates markdown todo files in the .planning/todos/pending directory with relevant metadata and content extracted from the conversation. Triggers include "add todo", "capture todo", "new todo", and "create todo".
adding-stacks
Use when adding a new framework/stack to create-faster CLI tool - addresses copy-first mentality, incomplete implementations, and missing dependencies
adding-phases
Use this skill to add planned work discovered during execution to the end of the current milestone in the roadmap. This skill appends sequential phases to the current milestone's phase list, automatically calculating the next phase number. Triggers include "add phase", "append phase", "new phase", and "create phase". This skill updates ROADMAP.md and STATE.md accordingly.
adding-persistent-event
Adds a new type of event that gets persisted to the event log. Use this when adding new kinds of write operations to the system or when adding new events to existing code.
adding-notes
Add new notes to the Second Brain knowledge base. Use when the user provides a resource (URL, book, podcast, article, GitHub repo, Reddit thread) and asks to "add a note", "create a note", "save this", "add to my notes", "take notes on", or "capture this".
/mnt/data2/nhlstats/.github/skills/adding-new-sport/SKILL.md
```markdown
adding-new-metric
Guides systematic implementation of new sustainability metrics in OSS Sustain Guard using the plugin-based metric system. Use when adding metric functions to evaluate project health aspects like issue responsiveness, test coverage, or security response time.
adding-new-ai-format
Step-by-step guide for adding support for a new AI editor format to PRPM - covers types, converters, schemas, CLI, webapp, and testing
adding-nango-provider-support
Use when adding support for a new Nango provider - configures provider in providers.yaml, creates documentation (main page, setup guide, connect guide), and updates docs.json following established patterns
adding-models
Guide for adding new LLM models to Letta Code. Use when the user wants to add support for a new model, needs to know valid model handles, or wants to update the model configuration. Covers models.json configuration, CI test matrix, and handle validation.
adding-mod-parsers
Use when adding new mod parsers to convert game mod strings to typed Mod objects - guides the template-based parsing pattern (project)