i18n
Skill9 starsChanged 5 days agoMITView on GitHub
Internationalization of Walph (pt-BR, English, Spanish): the shared message catalogs in src/shared/i18n, t() in main and useT() in the renderer, the workbench.language setting, locale-aware formatting and what is never translated. Use whenever code shows text to the user (JSX, toasts, errors thrown by main, dialogs, menus, quick picks, settings metadata) or formats numbers and dates.
50 other projects use a version of this.
Adopted by
Most recently taken up by
- elie222/inbox-zerotheir own version, first seen Nov 15, 2026
- haxsd/haxsd-byoktheir own version, first seen Nov 15, 2026
- lobehub/lobehubtheir own version, first seen Nov 15, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
- TheBeardedBearSAS/claude-crafttheir own version, first seen Nov 11, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use oss-pr, pr-automation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CES-LtdSkilloss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
Also in 3 projects that use this
CES-LtdSkillpr-automation
PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".
Also in 3 projects that use this
volovelySkillpr-fix
This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR comments", provides a GitHub PR URL with intent to fix, or says "pr-fix". It reads all review comments on a PR, decides which need code fixes vs. replies, makes the fixes, and posts replies — all with explicit user approval before any GitHub action.
Also in 3 projects that use this
GitHubSkillstate-management
CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.
Also in 4 projects that use this
xfstudioSkillgraphql
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
Also in 3 projects that use this
MicrosoftSkillbump-version
Bump the VoxelPic version to a user-specified value. USE FOR: setting or updating the project version across all files that embed it. Applies to requests like 'bump version to X.Y.Z', 'set version', or 'update version'.
Also in 4 projects that use this
- +2 more from CES-Ltd
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- lobehub/lobe-chat★ 86ksame name
- lobehub/lobehub★ 86ksame name
- iOfficeAI/AionUi★ 34ksame name
- elie222/inbox-zero★ 13ksame name
- massCodeIO/massCode★ 7.1ksame name
- leookun/cursor-byok★ 3.2ksame name
- Pixeval/Pixeval★ 3.2ksame name
- akiver/cs-demo-manager★ 2ksame name
- d-kimuson/claude-code-viewer★ 1.3ksame name
- huoshen80/ReinaManager★ 737same name
40 more not listed
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 repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- app-testingSkill
- claude-panelSkill
- commands-settingsSkill
- containersSkill
- debuggerSkill
- files-git-searchSkill
- lspSkill
- main-ipcSkill
- main-processesSkill
- packaging-releaseSkill
- renderer-componentsSkill
- renderer-editorSkill
- renderer-storeSkill
- renderer-stylesSkill
- renderer-terminalSkill
- workspacesSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 98
Prefer sending data/codes over IPC when the renderer formats the text itself.
- Very specific: line 126
No module-level translated constant.
“Common” is measured: kept by at least 6 in 10 of the 41 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.
Files
Internationalization (src/shared/i18n/)
The app ships in pt-BR, English and Spanish. Every user-visible string lives in a message catalog with the three translations; code never contains UI copy. pt-BR is the reference language (unit tests and E2E run in it).
Layout
| File | Role |
src/shared/i18n/locale.ts | LOCALES, Locale, LanguageSetting, current locale (getLocale/setLocale/onLocaleChange), resolveLocale (system languages → supported locale, fallback en) |
src/shared/i18n/define.ts | defineMessages (typed namespace with the 3 locales) and plural |
src/shared/i18n/format.ts | formatNumber, formatDate, formatList, compareText: always in the current locale |
src/shared/i18n/messages/<namespace>.ts | one namespace per domain (common, app, commands, menu, settings, quickInput, files, git, search, editor, lsp, snippets, terminal, containers, claudeHost, claude) |
src/shared/i18n/catalog.ts | registers the namespaces; Messages type |
src/shared/i18n/index.ts | public API: t(), LOCALE_NAMES and re-exports |
src/main/i18n/locale.ts | main applies workbench.language (user layer only) on every read of the user settings.json |
src/renderer/src/i18n.ts | useT() hook and applyLocale |
Flow: main resolves the locale (workbench.language, system = OS languages; WALPH_LOCALE env forces the "system"
language, used by E2E and launch.sh) → --walph-locale= argv on view creation (window.api.locale, first render
already translated) → SettingsSnapshot.locale on every change → applyLocale in the renderer (store locale,
<html lang>). Main rebuilds the native menu on onLocaleChange.
Writing a message
// src/shared/i18n/messages/git.ts
import { defineMessages, plural } from '../define'
export const git = defineMessages({
'pt-BR': {
pushFailed: (branch: string) => `Falha ao enviar ${branch}`,
changes: (n: number) => plural(n, '1 alteração', `${n} alterações`),
view: { title: 'Controle de código-fonte' }
},
en: {
pushFailed: (branch: string) => `Failed to push ${branch}`,
changes: (n: number) => plural(n, '1 change', `${n} changes`),
view: { title: 'Source Control' }
},
es: {
pushFailed: (branch: string) => `No se pudo enviar ${branch}`,
changes: (n: number) => plural(n, '1 cambio', `${n} cambios`),
view: { title: 'Control de código fuente' }
}
})enandesmust have exactly the pt-BR keys and signatures: a missing, extra or mistyped entry is a type error.- Keys in camelCase, grouped by component or flow (
git.view.title,git.errors.pushFailed). - Parameters are typed function arguments. One message per sentence: never glue translated fragments together
(word order differs between languages). Plurals with
plural(n, one, other)or an explicit ternary. - A sentence with inline markup (e.g.
<code>inside the text) is one string with{name}slots; the component splits it withsplitTemplate(src/renderer/src/lib/templateSlots.ts) and renders each slot as an element. - Generic words (OK, Cancel, Close, Save…) come from
common; everything else goes to the domain namespace. - New namespace = new file in
messages/+ one line incatalog.ts.
Using it
// main, actions, pure libs: resolve at call time
import { t } from '@shared/i18n'
throw new UserError(t().git.pushFailed(branch))
notify(t().git.changes(count))// React components: the hook re-renders on language change
import { useT } from '../i18n'
export function GitView(): React.JSX.Element {
const t = useT()
return <h2 title={t.git.view.title}>{t.git.view.title}</h2>
}Rules
- No UI literal in code: JSX text,
title/aria-label/placeholder/alt,notify(), toasts, errors thrown by main that reach the user, native dialogs, menu labels, quick pick items and details, status bar, settings labels, descriptions and validation warnings, empty states, CodeMirror/xterm widgets (EditorState.phrasesfor CodeMirror's built-in panels). - The rule is lint-enforced:
no-restricted-syntaxineslint.config.mjsrejects JSX text with 3+ letters and literaltitle/placeholder/aria-label/altinsrc/renderer/**/*.tsx(tests excluded). Only product names (Walph,Claude Code,Git,Docker) and the content of<code>/<kbd>/<samp>(commands, keys, setting keys) may stay literal; anything else goes throughuseT(). - Never resolve at module load: a module constant holding
t().xfreezes the language. Store keys or functions (label: () => t().settings.sections.editor), or build the list inside the function/component. useMemo/useCallbackthat produce text listtin their dependencies (each locale has its own catalog object).- Formatting via
formatNumber/formatDate/formatList/compareText; never hard-code'pt-BR'inIntlortoLocale*. - Main messages are produced in main's locale, which is the renderer's (both come from the user
settings.json). Prefer sending data/codes over IPC when the renderer formats the text itself. workbench.languageis a user-only setting (the native menu belongs to the whole app).
Never translated: code comments (English, per CLAUDE.md), console.* logs, IPC channels, setting keys, command ids,
text sent to Claude/the CLI/language servers, test fixtures, product and brand names (Walph, Claude Code, Git, Docker),
user content, key names produced by keybindingLabel.
Copy style per language
- pt-BR: the existing conventions (sentence case, verb first,
…for actions that open something). - en: Title Case for menu items, command titles and buttons, like VS Code ("Open Folder…", "Save All"); sentence case for descriptions, messages and errors.
- es: neutral Latin American Spanish, sentence case everywhere, VS Code terminology ("Abrir carpeta…", "Guardar todo", "Paleta de comandos", "Explorador", "Control de código fuente").
- Glossary: workspace → en "workspace", es "espacio de trabajo"; branch → "rama" (es); commit, stash, diff, pull, push stay in English in all three when pt-BR keeps them; Settings → "Configuración" (es).
Tests
- Unit tests run in pt-BR (
DEFAULT_LOCALE) and assert the pt-BR text. To cover another language:setLocale('en')in the test andsetLocale('pt-BR')inafterEach. src/shared/i18n/i18n.test.tschecks that every locale has the same keys and no empty text.- E2E and the
app-testingscripts force pt-BR withWALPH_LOCALE(e2e/helpers.tscleanEnv).
Checklist for new code
- Text added to the domain namespace in the three languages.
- Component uses
useT(); non-component code callst()at call time. - No module-level translated constant; memos depend on
t. - Numbers, dates and sorting through
format.ts. pnpm typecheckproves the three catalogs match.
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.

