i18n-translate
Skill1 starsChanged 4 months agoAGPL-3.0View on GitHub
Complete and maintain frontend i18n translations for this project. Covers finding missing translation keys, detecting untranslated entries, and adding translations for all supported locales (en, zh, zh-TW, fr, ja, ru, vi). Use for any task involving frontend locale files, missing translation keys, untranslated UI text, `t(...)` keys, `useTranslation()`, static i18n keys, button/label/ toast/dialog/placeholder/validation copy, or adding/fixing even a single i18n key. Use when review findings mention missing i18n, when new UI text needs translation, or when the user asks to add translations, fix i18n, or complete missing translations. Always load and follow this skill before translating, adding locale keys, or editing frontend i18n files.
8 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- QuantumNous/new-apiword for word, first seen Nov 15, 2026
- Gord1y/countersign-skillstheir own version, first seen Oct 11, 2026
- RocketChat/Rocket.Chat.Electrontheir own version, first seen Oct 8, 2026
- unorouter/new-apiword for word, first seen Sep 18, 2026
- MoleAPI/moleapiword for word, first seen Aug 27, 2026
- chatboxai/chatboxtheir own version, first seen Jul 28, 2026
Other versions8 projects use a version of this.
Word for word · 3
- QuantumNous/new-api★ 52k100% same
- unorouter/new-api★ 5100% same
- MoleAPI/moleapi★ 1100% same
Edited · 1
- lien0219/my-new-api★ 291% same
Wrote their own version · 4
- chatboxai/chatbox★ 42ksame name
- RocketChat/Rocket.Chat.Electron★ 1.7ksame name
- Gord1y/countersign-skills★ 2same name
- kasimmj/claude-skills-mega★ 1same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- shadcn-uiSkill
- vercel-react-best-practicesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 11 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.