agentleFS
0xOpCode0xOpCode/tele-harness/.agents/skills/i18n-builder/SKILL.md

i18n-builder

Skill1 starsChanged 50 days agoMITView on GitHub

Scaffolds internationalization dictionaries and locale detection middleware for Telegram bots.

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
  1. Distinctive:

    Follow these constraints when configuring multilingual support:

    line 9
  2. Very specific:

    Place locale dictionaries in /locales/{lang}.json or /locales/{lang}.ftl.

    line 12
  3. Distinctive:

    Never hardcode raw message strings in handler functions.

    line 15
  4. Very specific:

    Use structured keys: {domain}.{section}.{action} (e.g., onboarding.name_input.prompt).

    line 16
  5. Distinctive:

    Check user profile preference in database first.

    line 18
  6. Distinctive:

    Update database preference upon callback query receipt.

    line 23

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Internationalization Protocol

Follow these constraints when configuring multilingual support:

  1. Directory Structure:
    • Place locale dictionaries in /locales/{lang}.json or /locales/{lang}.ftl.
    • Maintain a canonical fallback language (en).
  2. String Extraction:
    • Never hardcode raw message strings in handler functions.
    • Use structured keys: {domain}.{section}.{action} (e.g., onboarding.name_input.prompt).
  3. 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.
  4. Language Switcher:
    • Provide an explicit /language command with InlineKeyboards showing native names (e.g., "English", "Español", "Русский").
    • Update database preference upon callback query receipt.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.