> Use when implementing translations/i18n in Frappe v14-v16 apps. Covers _() in Python, __() in JavaScript, CSV translation files, bench commands, string extraction rules, lazy translation _lt(), PO/MO files [v15+], RTL support, and custom app translations. Prevents common mistakes with f-strings, concatenation, and template literals that break string extraction. bench get-untranslated, RTL, localization.
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-translation
> Deterministic patterns for translating Frappe apps across v14, v15, and v16.
| Task | Python | JavaScript |
|------|--------|------------|
| Translate string | _("Hello") | __("Hello") |
| With substitution | _("Hello {0}").format(name) | __("Hello {0}", [name]) |
| With context | _("Change", context="Coins") | __("Change", null, "Coins") |
| Lazy (module-level) | _lt("Pending") [v15+] | N/A |
| Check RTL | frappe.utils.is_rtl() | frappe.utils.is_rtl() |
Need to translate a string?
├── In Python (.py)?
│ ├── Inside a function/method → _("text {0}").format(val)
│ ├── Module-level constant [v15+] → _lt("text")
│ └── Module-level constant [v14] → define inside function or use lazy
├── In JavaScript (.js)?
│ └── ALWAYS → __("text {0}", [val])
├── In Jinja template (.html)?
│ └── {{ _("text") }}
├── In Vue (.vue)?
│ └── __("text") in <script>, {{ __("text") }} in <template>
└── DocType label/description/option?
└── Auto-extracted — no _() needed
Where do translations live?
├── v14 → apps/{app}/{app}/translations/{lang}.csv
├── v15+ → apps/{app}/{app}/locale/{lang}/LC_MESSAGES/{app}.po
└── User overrides → Translation DocType (highest priority)
Need to extract untranslated strings?
├── v14 → bench --site {site} get-untranslated {lang} {output}
└── v15+ → bench generate-pot-file --app {app}
| Priority | Source | Scope |
|----------|--------|-------|
| 1 | Translation DocType (user overrides) | Per-site |
| 2 | MO files (locale/{lang}/.../{app}.mo) | Per-app [v15+] |
| 3 | CSV files (translations/{lang}.csv) | Per-app |
| 4 | Parent language (e.g., pt for pt-BR) | Fallback |
| Feature | v14 | v15 | v16 |
|---------|-----|-----|-----|
| _() / __() | Yes | Yes | Yes |
| _lt() lazy translation | No | Yes | Yes |
| CSV translations | Yes | Yes (legacy) | Yes (legacy) |
| PO/MO (gettext) | No | Yes | Yes |
| bench generate-pot-file | No | Yes | Yes |
| Babel JS extractor | No | Yes | Yes |
| Type hints on _() | No | No | Yes |
These are extracted automatically by the framework:
| File Type | Extractor | What It Finds |
|-----------|-----------|---------------|
| .py | Babel (AST) | _("..."), _lt("...") calls |
| .js | Babel tokenizer [v15+] / regex [v14] | __("...") calls |
| .html | Regex | {{ _("...") }} in Jinja |
| .vue | Same as JS | __("...") in script/template |
| .json | DocType parser | Labels, descriptions, options |
CRITICAL: Extractors work on the AST/tokens. They CANNOT extract dynamically constructed strings. See Anti-Patterns.
| Pattern | Why It Breaks | Correct Form |
|---------|---------------|--------------|
| _(f"Hello {name}") | f-string not extractable | _("Hello {0}").format(name) |
| _("Hello " + name) | Concatenation fragments | _("Hello {0}").format(name) |
| _("Welcome %s") % name | Old-style not extractable | _("Welcome {0}").format(name) |
| __(Hello ${name}) | Template literal not extractable | __("Hello {0}", [name]) |
| _(" Hello ") | Leading/trailing spaces trimmed | _("Hello") |
| _("item" if x else "items") | Ternary inside _() | _("item") if x else _("items") |
| _(variable) | Variable not extractable | _("Known String") |
> Full anti-pattern catalog with code examples: references/anti-patterns.md
Location: apps/{app}/{app}/translations/{lang}.csv
"source","translation","context"
"Hello","Hallo",""
"Change","Wisselgeld","Coins"
"Change","Wijziging","Amendment"
translations/ directoryLocation: apps/{app}/{app}/locale/{lang}/LC_MESSAGES/{app}.po
# Generate POT template
bench generate-pot-file --app {app}
# Migrate existing CSV to PO
bench migrate-csv-to-po --app {app}
# Compile PO to MO (required for runtime)
bench compile-po-to-mo --app {app}
PO files follow standard GNU gettext format. Use any PO editor (Poedit, Weblate, Transifex).
| Command | Version | Purpose |
|---------|---------|---------|
| bench --site {site} get-untranslated {lang} {output.csv} | All | Export untranslated strings |
| bench update-translations {lang} {untranslated.csv} {translated.csv} | All | Import translations |
| bench generate-pot-file --app {app} | v15+ | Generate .pot template |
| bench migrate-csv-to-po --app {app} | v15+ | Convert CSV to PO format |
| bench compile-po-to-mo --app {app} | v15+ | Compile PO to binary MO |
Hardcoded RTL languages: ar (Arabic), he (Hebrew), fa (Persian/Farsi), ps (Pashto)
# Python
if frappe.utils.is_rtl():
# Apply RTL-specific logic
// JavaScript
if (frappe.utils.is_rtl()) {
// Apply RTL-specific logic
}
dir="rtl" to the <html> elementmargin-inline-start not margin-left) for RTL compatibility_() / __() with positional placeholdersbench --site {site} get-untranslated {lang} untranslated.csvbench generate-pot-file --app {app}apps/{app}/{app}/translations/{lang}.csvapps/{app}/{app}/locale/{lang}/LC_MESSAGES/{app}.pobench compile-po-to-mo --app {app}bench --site {site} clear-cache| File | Contents |
|------|----------|
| references/api-reference.md | Full Python _() and JS __() API with all signatures and edge cases |
| references/csv-and-bench.md | CSV format spec, bench commands, PO/MO workflow, custom app setup |
| references/anti-patterns.md | Complete anti-pattern catalog with failing and corrected examples |
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take impertio-studio/frappe-core-translation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.