i18n-builder
Skill1 starsChanged 50 days agoMITView on GitHub
Scaffolds internationalization dictionaries and locale detection middleware for Telegram bots.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- create-db-schemaSkill
- fsm-builderSkill
- keyboard-navigatorSkill
- mini-app-builderSkill
- payment-gateway-setupSkill
- setup-webhookSkill
- tg-api-navigatorSkill
- tg-copywriterSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 9
Follow these constraints when configuring multilingual support:
- Very specific: line 12
Place locale dictionaries in /locales/{lang}.json or /locales/{lang}.ftl.
- Distinctive: line 15
Never hardcode raw message strings in handler functions.
- Very specific: line 16
Use structured keys: {domain}.{section}.{action} (e.g., onboarding.name_input.prompt).
- Distinctive: line 18
Check user profile preference in database first.
- Distinctive: line 23
Update database preference upon callback query receipt.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Internationalization Protocol
Follow these constraints when configuring multilingual support:
- Directory Structure:
- Place locale dictionaries in
/locales/{lang}.jsonor/locales/{lang}.ftl. - Maintain a canonical fallback language (
en).
- Place locale dictionaries in
- String Extraction:
- Never hardcode raw message strings in handler functions.
- Use structured keys:
{domain}.{section}.{action}(e.g.,onboarding.name_input.prompt).
- Locale Detection:
- Check user profile preference in database first.
- Fall back to
update.message.from.language_code. - Fall back to the default project locale if the user code is unsupported.
- Language Switcher:
- Provide an explicit
/languagecommand with InlineKeyboards showing native names (e.g., "English", "Español", "Русский"). - Update database preference upon callback query receipt.
- Provide an explicit
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.

