菜单
Manage translations and locale loading for the Web service using i18next-based middleware, server-injected template variables, and the client-side Translator helper.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | internationalization |
| description | Manage translations and locale loading for the Web service using i18next-based middleware, server-injected template variables, and the client-side Translator helper. |
Use this skill for internationalization, locale management, and translating error codes and template strings.
Locale files are stored by language and namespace:
web/locales/
en/
api-responses.json
pt/
api-responses.json
languageMiddleware (web/middleware/language.js) detects language from language cookie, Accept-Language header, or default fallback (en).renderMiddleware (web/middleware/render.js) loads requested namespace JSON files and embeds them into <script id="template-vars">.Translator helper (web/src/js/helpers/translate.js) reads injected translations via TemplateVar.get('translations') and wraps i18next.Instantiate Translator in browser page entries or components:
import { Translator } from './helpers/translate.js';
const translator = new Translator();
// Translate a key in a namespace
const title = translator.translate('title', 'index');
All REST API endpoints return a machine-readable code string (HTTP status codes >= 400) alongside default message strings. Localized translations for API error codes live in web/locales/<lang>/api-responses.json under the api-responses namespace.
Translate API errors using translator.translateApiError(errorPayload, 'api-responses'):
try {
await Item.create(data);
} catch (error) {
const message = translator.translateApiError(error);
new Toast(message, { tone: 'error' });
}
Resolution order:
code against api-responses namespace via i18next.message.message string if no key exists.Build or change API behavior in api/ using Express routers, middleware, CustomError, model instances, and camelCase JSON responses.
Review backend and frontend template code for real defects, boundary violations, security gaps, and missing tests. Auto-invoke for code reviews or bug investigations. Triggers: "bug review", "review code", "find bugs", "security audit", "check defects".
Implement OOP API entities in api/model/ using the shared Model base class and relation helper.
Maintain the api/helpers/postgres.js SQL boundary, CRUD helper surface, and safe filter conventions.
Update project-local agent guidance when architecture, workflows, commands, or conventions change. Auto-invoke when user or agent output indicates a reusable workflow or durable rule. Triggers: "update docs", "update skill", "create new skill", "update agent instructions", "document recurring pattern", "capture reusable workflow".
Add accurate JSDoc and focused comments when changing template code. Auto-invoke during code writing or refactoring. Triggers: "document code", "jsdoc", "code comments", "add comments", "explain logic".