Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

add-translations

Étoiles4 034

Forks1 294

Mis à jour29 mai 2026 à 05:29

Add or update erxes frontend translation keys and locale JSON entries. Use when a task introduces user-facing text, i18n namespaces, locale files, or translation hook usage.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

erxes

erxes/erxes

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	add-translations
description	Add or update erxes frontend translation keys and locale JSON entries. Use when a task introduces user-facing text, i18n namespaces, locale files, or translation hook usage.

Skill: Add Translations

Workflow

Check whether nearby UI already uses useTranslation and which namespace it uses.
Check frontend/core-ui/src/i18n/config.ts before adding a new namespace.
Add core UI strings under backend/gateway/src/locales/en/<namespace>.json and backend/gateway/src/locales/mn/<namespace>.json when the namespace exists in both languages.
Follow the namespace's existing key style, often kebab-case grouped by feature.
Use useTranslation(namespace, { keyPrefix }) when nearby code uses that pattern.
Use interpolation for dynamic values. Do not concatenate translated strings.
Verify JSON syntax and referenced namespace/key paths.

Important

Supported core languages are en and mn.
Prefer adding both English and Mongolian keys over relying only on fallback text for new user-facing UI.
Check long Mongolian strings in compact buttons, tabs, table headers, and drawer footers.
Do not add comments to JSON locale files.
For documentation-only translation edits, verify paths and keys instead of running full builds by default.

Plus depuis ce dépôt

même dépôt

create-backend-entity

erxes/erxes

Add or extend Mongoose-backed erxes backend entities, models, GraphQL schemas, resolvers, permissions, and metadata. Use for backend plugin or service feature work.

2026-06-144.0k

create-form-drawer

erxes/erxes

Build erxes drawer, sheet, or dialog forms with local validation, mutations, state, toasts, and close/reset behavior. Use for create and edit flows in frontend plugins.

2026-06-144.0k

create-page

erxes/erxes

Add erxes frontend pages and routes using nearby plugin page, layout, routing, loading, and feature-module structure. Use for route-level page work.

2026-06-144.0k

create-table

erxes/erxes

Build erxes table and list screens with existing RecordTable, cursor pagination, filters, loading states, actions, and command bar patterns.

2026-06-144.0k

create-plugin

erxes/erxes

Create a new erxes plugin from scratch. Scaffolds both frontend and backend with proper structure, config, and registration.

2026-05-294.0k

detect-scope

erxes/erxes

Detects user request intent, identifies target plugin/module, loads relevant code context, and asks minimal informed questions before proceeding to intake.

2026-05-294.0k

name	add-translations
description	Add or update erxes frontend translation keys and locale JSON entries. Use when a task introduces user-facing text, i18n namespaces, locale files, or translation hook usage.

Skill: Add Translations

Workflow

Check whether nearby UI already uses useTranslation and which namespace it uses.
Check frontend/core-ui/src/i18n/config.ts before adding a new namespace.
Add core UI strings under backend/gateway/src/locales/en/<namespace>.json and backend/gateway/src/locales/mn/<namespace>.json when the namespace exists in both languages.
Follow the namespace's existing key style, often kebab-case grouped by feature.
Use useTranslation(namespace, { keyPrefix }) when nearby code uses that pattern.
Use interpolation for dynamic values. Do not concatenate translated strings.
Verify JSON syntax and referenced namespace/key paths.

Important

Supported core languages are en and mn.
Prefer adding both English and Mongolian keys over relying only on fallback text for new user-facing UI.
Check long Mongolian strings in compact buttons, tabs, table headers, and drawer footers.
Do not add comments to JSON locale files.
For documentation-only translation edits, verify paths and keys instead of running full builds by default.