agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/game-localization/SKILL.md

game-localization

Skill13 starsChanged 24 days agoMITView on GitHub

Use when a game ships or tests multiple locales and string identity, glossary terms, plural/number formatting, glyph fallback, wrapping, layout, key prompts, subtitles, or runtime language switching can become inconsistent.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every translatable entry has a stable string ID independent from source text, translated text and table order.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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

Game Localization

This skill owns localized string identity, locale selection/fallback, formatting and language-specific content/layout validation. UI state/focus remains with UI skills; persistent dialogue facts remain with dialogue-flags.

Modes

ModeLocale behavior
single-localeone active shipping/test locale but still uses stable string IDs
terms-lockedmultiple locales with controlled glossary/terminology
live-switchlocale can change without restarting the full application/session

Every translatable entry has a stable string ID independent from source text, translated text and table order. Dynamic values use locale-aware formatting/plural rules; key/controller glyphs come from the active input mapping rather than baked text.

Publish locale fallback chains and font/glyph fallback behavior. Missing strings/glyphs produce inspectable fallback/error evidence; release severity is determined by the project's shipping criteria, not by this skill alone.

Glossary terms, body/display font roles, subtitle/caption strings and layout constraints are explicit. Test long/short strings, CJK/RTL where supported, plural/number/date cases, text scale and device/aspect matrices relevant to the product.

A live language switch updates localized presentation while preserving stable gameplay/save/entity IDs and current logical state. It must not reset combat, quest progress, focus owner or inventory because labels changed.

Acceptance

For each supported locale, verify stable string ID coverage, fallback/glyph coverage, representative dynamic formatting and critical UI/subtitle layouts. Switch locale at runtime when supported and confirm gameplay/save/focus state is unchanged. Screenshots match the active locale they claim, but screenshots alone are not string-coverage evidence.

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.