go-i18n
Skill18 starsChanged 7 months agoMITView on GitHub
Use when defining or updating Go CLI i18n rules in this repo, especially around locale files, env-based language selection, and key naming.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- find-skillsSkill
- finishing-a-development-branchSkill
- golang-cli-cobra-viperSkill
- golang-testingSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- skill-creatorSkill
- skills-xSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
- baidu-speech-to-textSkill
- feishu-notifySkill
- go-embedded-spaSkill
- go-pocketbase-integrationSkill
- minimal-ui-designSkill
- shadowrocket-claude-routingSkill
- skills-xSkill
- tui-designSkill
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 59
Use lowercase + underscores with category prefixes:
- Distinctive: line 70
Rule: Never mix Chinese and English in the same string.
- Distinctive: line 74
Add the same key to both locale files:
- Very specific: line 77
Use i18n.T / i18n.Tf in Go code.
- Very specific: line 85
Add a skill_<skill-name> key to both locale files.
- Distinctive: line 112
Only adding a key in one locale file
≈ “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
Go CLI i18n
Overview
This skill documents the Go CLI i18n rules used in this repo, including language detection, locale files, and key naming conventions.
When to Use
- You add or edit any user-facing CLI string in
cmd/skills-x - You need to add a new skill description for list output
- You are troubleshooting mixed language output or missing translations
Architecture Snapshot
- i18n runtime:
cmd/skills-x/i18n/i18n.go - Locale files:
cmd/skills-x/i18n/locales/zh.yaml,cmd/skills-x/i18n/locales/en.yaml - Embed:
//go:embed locales/*.yaml(locales are embedded at build time)
Language Selection
Priority order in detectLanguage():
SKILLS_LANGLANGLC_ALL- Default:
zh
Normalization uses prefix matching:
zh,zh_CN,zh_TW→zhen,en_US→en- Unsupported →
zh
Using i18n in Go
Initialize once (early in main):
import "github.com/castle-x/skills-x/cmd/skills-x/i18n"
i18n.MustInit()Translate strings:
title := i18n.T("list_header")
msg := i18n.Tf("init_success", skillName)Missing keys return the key itself (useful for spotting gaps).
Key Naming Conventions
Use lowercase + underscores with category prefixes:
app_app metadatacmd_command descriptions/flagslist_list outputinit_init outputerr_error messagescat_category namesskill_skill descriptionsmeta_meta warnings
Rule: Never mix Chinese and English in the same string. Use two locale keys instead.
Adding New Strings
- Add the same key to both locale files:
cmd/skills-x/i18n/locales/zh.yamlcmd/skills-x/i18n/locales/en.yaml
- Use
i18n.T/i18n.Tfin Go code. - Rebuild (
make build) to embed the updated YAML. - Test:
SKILLS_LANG=zh ./bin/skills-x listSKILLS_LANG=en ./bin/skills-x list
New Skill Description
Add a skill_<skill-name> key to both locale files. The list view reads descriptions from i18n, not from the skill file.
Example
# locales/en.yaml
init_success: "Installed: %s"
# locales/zh.yaml
init_success: "安装成功: %s"fmt.Println(i18n.Tf("init_success", skillName))Quick Reference
| Item | Value |
| Locale files | cmd/skills-x/i18n/locales/{zh,en}.yaml |
| Init | i18n.MustInit() |
| Translate | i18n.T, i18n.Tf |
| Language priority | SKILLS_LANG > LANG > LC_ALL > zh |
Common Mistakes
- Only adding a key in one locale file
- Hardcoding mixed-language strings
- Forgetting to rebuild after YAML changes
- Formatting with
fmt.Sprintfbefore callingi18n.Tf
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.

