# Svintl
> svintl CLI for i18n — translations, locales, pluralization, mounts, building typed dictionaries. Triggers on `npx intl`, YAML locale files, intl directories, or any translation/i18n work in Svelte projects.
- Skill: `temich/svintl` (Agent Skill)
- Install (CLI): `npx skillmds@latest add temich/svintl`
- Raw SKILL.md: https://api.skillmd.com/api/skills/temich/svintl/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: temich (https://skillmd.com/u/temich)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/temich/svintl
---
# svintl — i18n for Svelte
CLI tool for managing internationalization dictionaries with automatic translation via OpenAI.
## Core Rule
The `*.yaml`, `built.js`, and `types.ts` files in intl directories are generated — they're edited through the `npx intl` CLI, not by hand.
## CLI Commands
```bash
npx intl hola # init dictionaries (default: src/lib/intl/)
npx intl hola -p ./custom/path # init at custom path
npx intl add key.path "Value" "context" # add a new key — fails if it already exists; context optional
npx intl set key.path "Updated value" # update a key that already exists — fails if missing
npx intl set "mount/key.path" "Value" # target a mount with the mount/ prefix
npx intl add key.path "Value" --debug # --debug (add or set): print the OpenAI request first
npx intl const key.path "Same everywhere" # same value across all locales (no translation)
npx intl unit items.count "item" # pluralized entry (auto-generates plural forms)
npx intl move old.key new.key # rename key/branch
npx intl del key.path # delete key/branch
npx intl create es # add a locale (BCP 47 tag) — auto-translates the whole dictionary into it
npx intl destroy es # delete locale
npx intl mount foo ./any/path # create empty mount
npx intl import foo ./any/path # adopt existing dict dir as mount, reconcile locales
npx intl unmount foo # remove mount (keeps files)
npx intl context "Project description" # set project-wide translation guidance
npx intl context --clear # clear project context
npx intl genders he she none # enable gender-aware translations (list the gender values)
npx intl genders # print current gender values
npx intl sync en key.path # reconcile: re-translate one key into all locales from source en
npx intl sync en # reconcile: re-translate the whole dictionary from source en
npx intl build # rebuild JS/TS from YAML
```
## Dictionary Format
YAML with arbitrary nesting, strings at leaves:
```yaml
native: English
example:
hello: "Hello world"
```
Usage: `{$dict.example.hello}`
### Dynamic Values — Placeholders
For simple cases the CLI auto-generates `!js` functions from placeholder syntax — no need to write them manually:
```bash
npx intl set greeting "Hello, {name}!" # {name} → function param
npx intl set joined "[names] joined {groupName}" # [names] → Intl.ListFormat
```
For complex logic, pass `!js` functions via `intl set`:
```bash
npx intl set greeting '!js (count) => `${count || "No"} item${count === 1 ? "" : "s"}`'
```
Usage in components: `{$dict.greeting(user.name)}`
**Keep the whole phrase in the dictionary.** Never split a sentence around a dynamic value in the template:
```svelte
{brand}{$dict.form.destroyDescription}
{@html $dict.form.destroyDescription(brand)}
```
```bash
npx intl set "apps/form.destroyDescription" \
'!js (brand) => `${brand} and all accumulated data will be permanently deleted.`'
```
When a name needs markup and is always at the start of the phrase across languages, put the tags inside the `!js` function and render with `{@html}` — escape user-controlled values before passing them in.
### Pluralization
Use `npx intl unit` — generates `Intl.PluralRules`-based functions:
```bash
npx intl unit items.count "item"
```
Produces:
```yaml
items:
count:
- one: item
other: items
```
Usage: `{$dict.items.count(count)}`
Complex locales (Russian, Arabic) auto-get `few`, `many`, etc.
### Genders
When enabled (`npx intl genders he she none`), gender-dependent phrases become functions whose **last** argument is the gender (`'he' | 'she' | 'none'`) — the phrase's own arguments come first, e.g. `(name, gender) => …`. The listed values become the generated `Grammar` union.
## Mounts
Organize translations into separate directories:
```bash
npx intl mount admin ./src/features/admin/intl
npx intl set "admin/dashboard.title" "Admin Dashboard"
```
Mount keys use `{mount}/` prefix in CLI commands.
`mount` scaffolds an empty mount; `import` adopts a populated dir (with its own `context.yaml`) and reconciles its locales to the root — drops languages the root lacks, generates ones it lacks (translating the imported `inputs`), leaves shared locales untouched.
## Import Pattern
**Root dictionary:**
```svelte
{$dict.example.hello}
```
**Mount dictionary:**
```svelte
{$dict.dashboard.title}
```
**Mount's `intl/index.ts`:**
```typescript
import { derived } from 'svelte/store'
import { locale } from '$lib/intl'
import { dictionaries } from './built.js'
import type { Locale, Dictionary } from './types'
const dict = derived(locale, ($locale) => dictionaries[$locale])
export { dict, dictionaries, locale }
export type { Locale, Dictionary }
```
## Context for Translation Accuracy
```bash
npx intl set app.welcome "Welcome" "greeting shown on homepage"
npx intl context "B2B SaaS for enterprise users"
```
Context is stored in `context.yaml` and used by OpenAI when creating new locales.
## Workflow
1. Use `npx intl add/set/unit/const` to add/update translations
2. Run `npx intl build` to generate JS/TS (often auto-runs)
3. Import `dict` store in components
4. Use `$dict.key.path` in templates
## Avoid
- **Editing YAML by hand** — go through the CLI
- **`npx intl sync` for routine edits** — it's only for reconciling after a manual source edit; use `add`/`set` instead
- **Non-BCP47 locale codes** — use valid tags like `en-US`, `es`, `pt-BR`
- **Splitting phrases in the template** — don't concatenate a dynamic value with a dictionary suffix/prefix; use one `{placeholder}` / `!js` entry for the full sentence