i18n-parity
Skill2 starsChanged 2 months agoMITView on GitHub
Checks internationalization parity — that every translation key exists in all locales and that no user-facing strings are hardcoded — following the project's i18n conventions. Use this when the user asks to check translations, verify locale parity, find missing/hardcoded strings, or audit i18n (e.g. "check i18n", "are all locales in sync?").
3 other projects use a version of this.
Adopted by
Most recently taken up by
- brayandiazc/project-starter-template-es-aitheir own version, first seen Sep 7, 2026
- hoangsonww/Claude-Code-Agent-Monitortheir own version, first seen Aug 5, 2026
- dougmotshell/mathematics-studiestheir own version, first seen Aug 1, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- hoangsonww/Claude-Code-Agent-Monitor★ 1.2ksame name
- brayandiazc/project-starter-template-es-ai★ 15same name
- dougmotshell/mathematics-studies★ 0same name
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- changelogSkill
- commitSkill
- configure-repoSkill
- copywritingSkill
- design-system-auditSkill
- identitySkill
- instantiateSkill
- migration-guardSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- open-prSkill
- port-changeSkill
- prototypeSkill
- releaseSkill
- seo-auditSkill
- update-templateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Verify locale parity and catch hardcoded user-facing strings.
- Very specific: line 8
Read docs/conventions/i18n.md for the locale file format, where translation files live, the default/reference locale, and the rule for what …
- Very specific: line 18
Do NOT auto-translate or invent translation text — report gaps so a human/translator fills them.
≈ “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.
Files
Verify locale parity and catch hardcoded user-facing strings.
- Read
docs/conventions/i18n.mdfor the locale file format, where translation files live, the default/reference locale, and the rule for what must be translated. - List the locale files and treat the reference locale as the source of truth for the key set.
- Compare keys across locales:
- Keys present in the reference but missing in another locale → report as missing.
- Keys present in a locale but not in the reference → report as orphaned.
- Empty or untranslated-but-identical values → flag for review.
- Scan UI source for hardcoded user-facing strings that should go through the i18n system (per the convention's rules), and list each with file:line.
- Optionally run the bundled helper
scripts/check.sh(relative to this skill) for a quick automated pass — but note it is a STUB the user must adapt to their actual i18n format before relying on it. - Report a summary: missing keys per locale, orphaned keys, and suspected hardcoded strings.
Do NOT auto-translate or invent translation text — report gaps so a human/translator fills them. Always defer to docs/conventions/i18n.md.
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
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.

