Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Internationalization conventions for Stella. An agent skill from stella/stella.
Install Conventions I18n
$ npx skills add stella/stella --skill conventions-i18n -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stella/stella conventions-i18n --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/conventions-i18n .claude/skills/conventions-i18n && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .claude/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18nType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stella/stella --skill conventions-i18n -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stella/stella conventions-i18n --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/conventions-i18n .agents/skills/conventions-i18n && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .agents/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stella/stella --skill conventions-i18n -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stella/stella conventions-i18n --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/conventions-i18n .cursor/skills/conventions-i18n && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .cursor/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stella/stella.git --path .agents/skills/conventions-i18n--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stella/stella --skill conventions-i18n -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stella/stella conventions-i18n --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/conventions-i18n .gemini/skills/conventions-i18n && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .gemini/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stella/stella conventions-i18nInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stella/stella --skill conventions-i18n -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/conventions-i18n .github/skills/conventions-i18n && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .github/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stella/stella --skill conventions-i18n -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stella/stella conventions-i18n --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/conventions-i18n .opencode/skills/conventions-i18n && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conventions-i18n" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/conventions-i18n into .opencode/skills/conventions-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventions-i18n", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
conventions-i18n- GitHub stars
- 258
- Token cost
- ~1.4k tokens
- SKILL.md length
- 751 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Internationalization conventions for Stella. An agent skill from stella/stella.
- Works in 5 steps: Add or modify keys in → Add corresponding translations to all… → Run bun run i18n:sync from apps/web.… → …
- Tasks that involve Internationalization
- SKILL.md covers Stack, Supported Languages, Translation Flow and Key Naming, plus 2 more sections
- Calls bun
What it does
Conventions I18n is an agent skill from stella/stella. Internationalization conventions for Stella. Apply when adding or modifying user-facing strings.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Internationalization. The repository describes itself as: Open-source legal workspace. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Internationalization
Example prompts
- “/conventions-i18n”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Add or modify keys in
- Add corresponding translations to all target language files
- Run bun run i18n:sync from apps/web. This synchronizes locale
- Run bun run i18n:check from apps/web. Typecheck does not regenerate or
- Read the rendered sentence in context, including interpolation and plural
What it can do on your machine
Read from SKILL.md and the folder at commit a9618db. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conventions I18n loads about 1.4k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 751 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from stella/stella at commit a9618db, republished under its Apache-2.0 licence (© stella). 751 words, ~1,442 tokens.
Download SKILL.mdSave it as
.claude/skills/conventions-i18n/SKILL.md (or your agent's skills folder).- name
- conventions-i18n
- description
- Internationalization conventions for Stella. Apply when adding or modifying user-facing strings.
i18n Conventions
Internationalization conventions for Stella. Apply when adding or modifying user-facing strings.
Stack
use-intl for runtime.
Supported Languages
en is the source language. Check apps/web/src/i18n/langs/ for
the current list of target languages (add translations to every
.json file found there).
Translation Flow
- Add or modify keys in
apps/web/src/i18n/langs/en.json. - Add corresponding translations to all target language files
found in
apps/web/src/i18n/langs/(every.jsonfile excepten.json). Write natural, idiomatic translations; avoid literal/robotic phrasing. - Run
bun run i18n:syncfromapps/web. This synchronizes locale structure, regenerates typed messages, and updates generated glossary output. Never editmessages.gen.tsor generated terminology tables by hand. - Run
bun run i18n:checkfromapps/web. Typecheck does not regenerate or validate the catalogs, so a clean typecheck is not evidence that i18n is in sync. - Read the rendered sentence in context, including interpolation and plural branches. Passing key parity is not proof that a translation is natural or that placeholders remain grammatically valid.
Key Naming
Prefer generic, reusable keys over feature-specific ones.
Before adding any new i18n key, search en.json for an existing
key with the same or similar wording (e.g., common.filter,
common.sort, common.columns). Reuse common.* or shared
namespace keys instead of creating feature-scoped duplicates
like billing.expenses.deleteExpense. Feature-specific keys
are only justified when the wording truly differs from the
generic version (e.g., a confirmation message that mentions
the resource by name).
When a translation key crosses indirection through a constant, map, prop, or
helper return type, type it with TranslationKey from
apps/web/src/i18n/types.ts instead of string. Missing or stale keys must
fail typecheck at the point where they are stored.
Prefer complete translatable sentences over fragments assembled in JSX. Keep
interpolation variables semantic ({documentName}, not {value}), use ICU
plural/select branches for grammatical variation, and never concatenate
translated fragments whose word order differs by locale.
Never call anything an "entity" in user-facing copy, in English or as a
calque (entita, Entität, entidad, entité, entidade, encja, ...).
It is the database's word for a row and means nothing to a lawyer. Name the
concrete thing the string is about — document, file, folder, task, matter —
and fall back to "item" only when the string genuinely covers all of them. In
anonymization, what the detector finds is a match, not an entity. The
item concept in glossary.json enforces this with forbiddenAlways, so it
fires on the English source too, not only on translations.
Key naming, pluralization, and style rules are documented
in apps/web/src/i18n/TERMINOLOGY.md.
Show full SKILL.md (349 more words)Show less
Terminology (glossary)
Canonical legal/domain terms live in
apps/web/src/i18n/glossary.json (the source of truth);
glossary-gen renders them into the tables in TERMINOLOGY.md.
The i18n-lint checker enforces them: per concept it flags a
translation that uses a forbidden rendering when the English
source is about that concept (concept-gated, so a common word only
fires in the right context).
When introducing a NEW concept (or changing a preferred term):
- Research it first. Confirm the sector-standard term and the
synonyms to avoid in each language against authoritative
sources (IATE/EU terminology, national legal glossaries,
established legal-tech usage) — do not guess. Record the
rationale in the concept's
note. - Add it to
glossary.json, never only toTERMINOLOGY.md(the.mdis generated). Runbun run i18n:sync(fromapps/web) to regenerate the tables. - Account for declensions/inflections. The lint matches
forbidden terms whole-word (English source triggers also match
their regular plural), so list the actual inflected, declined,
and compound forms a translator might use — e.g. de
Sache/Sachen/Mandatsdaten, skVec/veci/vecou, etasi/asja/asjad. A base form alone misses inflected drift. - Pick the right ban field.
forbiddenis concept-gated: it fires only where the English source names the concept (or akeyTriggerspath matches), which is what stops a common word from false-firing everywhere.forbiddenAlwaysdrops that gate, for wording that is wrong in every context. Use it when a concept-gated ban would go blind the moment someone rewords the English source, and only once you have checked that no legitimate use of the word exists in that locale. - Apply consistently.
bun run i18n:checkfails on new forbidden renderings; fix the translations, or — only for genuine pre-existing debt — grandfather withi18n-lint <dir> --write-baselineand flag for native review.
Landing (marketing) catalogs
The landing app has its own catalogs (apps/landing/src/i18n/messages/)
with the same glossary enforcement plus marketing-specific rules —
register per locale, the identity phrase, hero structure differences,
meta-string length budgets, cognate policy, and brand handling. Before
translating landing strings, read
apps/landing/src/i18n/TRANSLATION.md; it explains the intent behind
each rule so translations stay coherent rather than merely passing the
checks. Landing gates: bun run i18n:sync and bun run i18n:check
from apps/landing.
© stella, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/conventions-i18n of stella/stella.
Open the folder on GitHubat commit a9618db
Compare with similar skills
Conventions I18n next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conventions I18n this skillstella/stella | 258 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Chatbox i18n Translatorchatboxai/chatbox | 42k | — | ~508 | Automated safety check: Pass | GPL-3.0 | |
| Internationalization Workflow with i18niOfficeAI/AionUi | 33k | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Enforce Rules For I18nmoeru-ai/airi | 50k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Claude Desktop Chinese Localizationjavaht/claude-desktop-zh-cn | 7.5k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Chatbox i18n Translator
chatboxai/chatbox
Translates new or changed i18n keys from a Chatbox Pro diff, staged changes or a commit range, writing the locale JSON files directly with a built-in glossary.
Internationalization Workflow with i18n
iOfficeAI/AionUi
Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules.
Enforce Rules For I18n
moeru-ai/airi
Review pending AIRI translations on Crowdin in a batch, then sync them into the repository.
Claude Desktop Chinese Localization
javaht/claude-desktop-zh-cn
Adds missing Simplified and Traditional Chinese translations to the Claude Desktop Chinese patch across three layers, then checks how many mappings actually hit.
Taro UI Guide
jd-opensource/taro-ui
Guides installing, configuring, styling and using taro-ui (At* components) in Taro apps for WeChat, Alipay, H5 and React Native.
More from stella/stella
All 24 skills in this repoPlan
stella/stella
Create a concise, evidence-backed implementation plan in the repository planning area when the user explicitly asks for a plan.
Answer From Sources
stella/stella
Answers data-protection (GDPR) questions grounded in the regulation and supervisory guidance, with a citation for every claim.
Check Against Rules
stella/stella
Reviews a non-disclosure agreement against the firm's NDA checklist and reports findings with citations.
Intake To Draft
stella/stella
Collects the facts of an unpaid invoice, then drafts a payment demand letter.
Conventions Perf
stella/stella
Apply when a performance-guard check (network baseline, bundle baseline, DB query count, loader-prefetch lint, RC bailouts) fails or when touching a hot route/endpoint.
Conventions Use Effect
stella/stella
Apply when writing or reviewing React effects in apps/web. An agent skill from stella/stella.
Related
Categories
Questions about Conventions I18n
What does Conventions I18n do?
Internationalization conventions for Stella. An agent skill from stella/stella. Conventions I18n is an agent skill from stella/stella. Internationalization conventions for Stella.
When should I use Conventions I18n?
Conventions I18n fits situations like: tasks that involve Internationalization.
How do I install Conventions I18n in Claude Code?
Run `npx skills add stella/stella --skill conventions-i18n -a claude-code`. Or copy the skill folder (.agents/skills/conventions-i18n in stella/stella) into .claude/skills/conventions-i18n in your project. Claude Code loads it when a task matches its description.
How do I install Conventions I18n in Codex?
Run `npx skills add stella/stella --skill conventions-i18n -a codex`. Or copy the skill folder (.agents/skills/conventions-i18n in stella/stella) into .agents/skills/conventions-i18n in your project. Codex loads it when a task matches its description.
Can I use Conventions I18n in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stella/stella --skill conventions-i18n -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conventions-i18n, .gemini/skills/conventions-i18n, .github/skills/conventions-i18n and .opencode/skills/conventions-i18n in your project.
What does Conventions I18n need to run?
Going by SKILL.md and its folder, Conventions I18n needs the command-line tools its instructions call (bun).
Does Conventions I18n access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Conventions I18n safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conventions I18n use?
Conventions I18n is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conventions I18n use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Conventions I18n?
Skills that share tags, products or a category with Conventions I18n: Impeccable (bestofjs/bestofjs, 3.1k stars), Chatbox i18n Translator (chatboxai/chatbox, 42k stars), Internationalization Workflow with i18n (iOfficeAI/AionUi, 33k stars) and Enforce Rules For I18n (moeru-ai/airi, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventions I18n?
stella (a GitHub organization) maintains it in stella/stella, which has 258 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 10, 2026.
Source: stella/stella on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.