菜单
Add mirrored Arabic + English translation keys to src/infrastructure/i18n/translations/{ar,en}/<feature>.json, then regenerate translation-keys.ts via npm run i18n:sync. Triggers: "add a translation", a Translator.tr('<key>') call without a matching JSON key, "/add-i18n-keys".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add an HTTP endpoint to an existing module — updates the audience-scoped controller (creates one if needed), DTO, service method, and i18n keys for any new error messages. Triggers: "add an endpoint", "expose endpoint X on module Y", "add a route to <module>", "/add-endpoint".
Add a TypeORM entity to an existing module — entity file, repository, TypeOrmModule.forFeature registration, generated migration. Triggers: "add an entity", "add a table", "add <Entity> to module X", "/add-entity".
Generate a new role-scoped controller for an existing module (e.g. admin-foo.controller.ts next to user-foo.controller.ts). Wires @Protected(Role.X), the path/version, and registers in the module. Triggers: "expose this module to admins/users", "add an admin controller for <module>", "/add-protected-controller".
Diagnose and break a circular dependency between NestJS modules or providers — without reaching for forwardRef. Triggers: Nest "circular dependency" / "can't resolve dependencies" startup error, "ModuleA imports ModuleB and back", a new cross-module service injection, "how do I avoid a cycle", "/circular-deps".
Apply when writing, reviewing, or removing comments. Triggers: /comments, "should I comment this", "is this comment good", "explain why this code does X".
Generate or update a Postman Collection v2.1.0 JSON for a single module. The collection lives at `src/modules/<module>/postman/<module>.postman_collection.json`. Triggers "generate postman collection for X", "/generate-postman-collection <module>".
| name | add-i18n-keys |
| description | Add mirrored Arabic + English translation keys to src/infrastructure/i18n/translations/{ar,en}/<feature>.json, then regenerate translation-keys.ts via npm run i18n:sync. Triggers: "add a translation", a Translator.tr('<key>') call without a matching JSON key, "/add-i18n-keys". |
Add one or more translation keys to the AR and EN files for a feature, then run the validator that regenerates the typed key list.
<feature> — namespace == JSON filename (city, area, user, common). Snake_case filenames map to dotted keys (refresh_token.json → refresh_token.<...>).<dot.path> — key path inside the namespace (errors.not_found, success.created, validation.phone.invalid).<ar-value> / <en-value> — translated strings. Use {placeholder} for nestjs-i18n interpolations.<path> <ar> <en> triplets are accepted to batch.If the user gave a free-form list, parse it into triplets and confirm once before writing.
src/infrastructure/i18n/translations/{ar,en}/<feature>.json exist.
{} and proceed.<dot.path>, check it doesn't already resolve in either file. If it does, ask before overwriting.{property} in one but not the other).For each key:
Only the JSON node you touch may change. Never reformat the rest.
npm run i18n:sync
Validates AR↔EN parity (no orphan keys, identical placeholder sets) and regenerates src/infrastructure/i18n/translation-keys.ts (TranslationKey union + TranslationInterpolations map).
Never edit translation-keys.ts by hand — it's overwritten on every run.
If validation fails: read the report, fix the JSON (missing mirror key, placeholder typo, JSON parse error), re-run.
If the keys are added to support already-written code:
npm run build
The build now type-checks the Translator.tr('<feature>.<path>') calls.
✓ Added <N> key(s):
- <feature>.<path> → AR: "<ar>" EN: "<en>"
...
✓ Regenerated infrastructure/i18n/translation-keys.ts
✓ npm run build green
{property} (camelCase DTO property name).{min}, {max} — emitted automatically by Translator.trValMsg(...)."City not found."), not a {entity} placeholder.infrastructure/i18n/translation-keys.ts.common.validation.* or common.errors.* covers it.