i18n-strings
Skill501 starsChanged 17 days agoApache-2.0View on GitHub
Audit and fix untranslated user-visible text — titles, headings, button and menu labels, aria-label/title/placeholder/alt, empty states, errors, tooltips. In libs/* every string comes from a `*Labels` prop with an English default and the lib never imports i18n; in apps/chat every string is `t()` with a key from `translation-keys.ts`, and every lib `*Labels` field the app renders is filled with `t()`. Finds JSX text and literal text attributes in libs and the app, raw `t('…')` keys, i18n imports in libs, and lib label fields the app never passes. Use to check all libs and the app, one lib, or the current branch.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- beydemirfurkan/todoxtheir own version, first seen Sep 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- beydemirfurkan/todox★ 2same name
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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/a11y.mdcCursor rule
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- address-current-branch-reviewSkill
- api-designSkill
- celebration-scene-ideasSkill
- code-review-and-qualitySkill
- create-ticketSkill
- dep-scanSkill
- dep-triageSkill
- dial-docsSkill
- extract-to-libSkill
- figmaSkill
- fix-cve-backportSkill
- git-shipSkill
- lean-verificationSkill
- lib-themingSkill
- monitor-ciSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- proactive-security-monitorSkill
- refactoring-auditSkill
- chat-release-notesSkill
- responsive-designSkill
- security-monitor-triagerSkill
- snyk-jira-ingestSkill
- snyk-scan-stubSkill
- snyk-triageSkill
- ui-kit-reviewSkill
- nx-generateSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every string a user reads or hears is translated.
- Very specific: line 16
Every user-visible string — JSX text, a heading or title, aria-label, title, placeholder, alt, a tooltip, an empty state, an error or a …
- Very specific: line 38
Every label field is forwarded to the component that renders it (libs.md "Every declared prop must be read").
- Very specific: line 43
Every string is t(SomeI18nKeys.Member): the key is declared in a string enum in apps/chat/src/constants/translation-keys.ts and in …
- Very specific: line 47
Every *Labels field of a lib component the app renders is passed, built with t() — usually in a build*Labels(t) helper or a useMemo next to …
- Distinctive: line 80
Scan: Run the scanner in the requested mode.
- Very specific: line 111
Add the field to the component's *Labels interface with an inline JSDoc quoting the English default verbatim.
- Very specific: line 119
Add an enum member to the right enum in apps/chat/src/constants/translation-keys.ts (reuse a ButtonsI18nKeys member when the English string …
- Very specific: line 122
Add the key to apps/chat/src/i18n/locales/en.json with the English text, matching the lib default.
≈ “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
i18n strings
Every string a user reads or hears is translated. Libs never translate; they
expose the text as props with English defaults, and the app fills every one of
them through t().
The rule
In libs/*:
Every user-visible string — JSX text, a heading or title,
aria-label,title,placeholder,alt, a tooltip, an empty state, an error or a notification — comes from alabelsprop (*Labels, or a*Texts/*AriaLabelsgroup) with an English default:export interface ShareDialogLabels { /** Dialog title. Defaults to `'Share'`. */ title?: string; /** Accessible name of the close button. Defaults to `'Close'`. */ closeAriaLabel?: string; } <h2 className={titleClassName}>{labels?.title ?? 'Share'}</h2> <IconButton aria-label={labels?.closeAriaLabel ?? 'Close'} />- A string with values in it is a formatter (
(count: number) => string) or a template with named placeholders the lib fills ('Version {version}') — never English assembled from fragments, because word order differs by language. - The lib never imports
react-i18next/i18nextand never reads the language (.claude/rules/libs.md"No i18n inside libs"). - Every label field is forwarded to the component that renders it
(
libs.md"Every declared prop must be read").
In apps/chat:
- Every string is
t(SomeI18nKeys.Member): the key is declared in a string enum inapps/chat/src/constants/translation-keys.tsand inapps/chat/src/i18n/locales/en.jsonin the same change — never a rawt('a.b')key and never a literal (.claude/rules/all-ts.md). - Every
*Labelsfield of a lib component the app renders is passed, built witht()— usually in abuild*Labels(t)helper or auseMemonext to the render. A field the app leaves out shows the lib's English default to every user, whatever their language. - Reuse a generic key (
ButtonsI18nKeys.Cancel,.Save,.Copy) before adding a feature-scoped duplicate (all-ts.md"Avoid duplicate translation values").
Inputs
| Mode | Command |
| Everything | node .claude/skills/i18n-strings/scan.mjs — all libs and apps/chat, the default |
| Some scopes | node .claude/skills/i18n-strings/scan.mjs catalog chat (chat means apps/chat) |
| This branch | node .claude/skills/i18n-strings/scan.mjs --base origin/development (branch + uncommitted) |
| Machine | add --json |
The scanner skips tests, stories and chat-api-client.
Signals
| Signal | Means |
jsx-literal-text | prose written straight into JSX: >Save<, {'Save'}, or a line of text between JSX lines |
literal-text-attr | a text prop or attribute (title, aria-label, placeholder, alt, label, tooltip, description, message, heading, …) set to a literal string; a template built only from props (${labels.x} ${n}) is skipped |
raw-translation-key | apps/chat calls t('…') with a string instead of an enum member |
literal-text-field | apps/chat sets a text field of an object (message, title, label, *Label, *Message, …) to an English literal — a label map, an error or a notification built without t() |
i18n-in-lib | a lib imports react-i18next or i18next |
label-not-translated | a text field (string or => string) of a lib *Labels / *Texts / *AriaLabels interface whose name appears nowhere in apps/chat/src, for a lib the app imports — the user always sees the English default |
duplicate-translation-value | the same English text under two keys of apps/chat/src/i18n/locales/en.json (plural forms _one/_other of one key are ignored). With --base, only groups with a key the branch added |
Workflow
- Scan. Run the scanner in the requested mode. With no scope given, scan everything and report the per-scope totals first.
- Verify each hit in context. A hit is a candidate. Drop it when:
- the text is not user-visible: a test id, a log line, a URL, a CSS value, a key, code shown as code.
- it is a brand or product name that is never translated (
DIAL,OpenAI) — say so in the report. - a
label-not-translatedfield is filled under another name (the app spreads a helper whose keys are built dynamically, or a parent lib fills it from its own label). Search the app for the interface name and the component before reporting it. - a
label-not-translatedfield belongs to a component the app does not render at all. - a
literal-text-fieldis a machine-facing message: an error object with acodereturned through the overlay protocol or an API, read by an integrator, never rendered. - a
duplicate-translation-valueis a context-specific word whose translation can differ by place (a filter "Shared" vs a folder "Shared", a section "Configuration" in two features). Keep it, and say why. A generic button or action label ("Save", "Retry", "Back", "Open in new tab") or the same full message in two features is never such a case: reuse theButtonsI18nKeysmember or one shared key.
- Report. Group by scope, then file:
path:line, the text, and the fix — which*Labelsfield it becomes in the lib, or which enum key anden.jsonentry it becomes in the app. Fix (only when asked).
In a lib:
- Add the field to the component's
*Labelsinterface with an inline JSDoc quoting the English default verbatim. - Render
labels?.field ?? 'English default'(or destructure with a default) and thread the field through every intermediate layer. - Export a new
*Labelstype fromsrc/index.tsand list the field in the lib README.
In
apps/chat:- Add an enum member to the right enum in
apps/chat/src/constants/translation-keys.ts(reuse aButtonsI18nKeysmember when the English string already exists — grepen.jsonfirst). - Add the key to
apps/chat/src/i18n/locales/en.jsonwith the English text, matching the lib default. - Pass it where the app renders the lib component, through the existing
build*Labels(t)helper oruseMemofor that component when there is one.
- Add the field to the component's
- Verify. Rerun the scanner on the touched scopes (expect the fixed hits
gone), then
npm exec nx run-many -- -t typecheck lint -p <@epam/pkg ...> @epam/chatandnpm run validate:docs. Nx project names are the package names.
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.

