القائمة
Use when changing Sho Metrics Hub internationalization, including Property Inspector user-visible copy, Stream Deck manifest locale JSON, i18n message groups, locale resolution, generated i18n scripts, supported locales, translation wording, or dev locale override behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when reading or writing any ShoMetrics log.
Use when changing or reviewing code that crosses major application boundaries such as settings, Property Inspector, actions, runtime sources/helpers, rendering, persistence, validation, generated contracts, IPC, version-skewed helper/plugin APIs, or adapters. Keep boundaries explicit and avoid over-engineered plumbing, option bags, duplicated models, and defensive code for impossible states.
Use when writing, reviewing, or changing code in this repo for language-neutral naming, ownership boundaries, comments/documentation, test structure, exception scope, and avoiding speculative abstractions; pair with language-specific skills such as typescript-coding-style or csharp-coding-style when applicable.
Use when writing, reviewing, or changing C#/.NET code in this repo, especially packages/source-windows Core, Helper, ControlPanel, .csproj, .editorconfig, NativeAOT, nullable, async/threading, and modern C# feature decisions. Pair with coding-style for language-neutral naming, comments, tests, and ownership rules.
Use when making or reviewing naming changes in this repo, including function verb choices, domain vocabulary, boundary vocabulary, file/type/export names, stored/resolved/settings field names, renderer contract names, and historical vocabulary cleanup.
Use when changing lifecycle hooks, polling, rendering, caching, startup, IPC, benchmarks, throttling, queueing, or any code that may run often enough to affect responsiveness or resource usage.
استنادا إلى تصنيف SOC المهني
| name | hub-i18n |
| description | Use when changing Sho Metrics Hub internationalization, including Property Inspector user-visible copy, Stream Deck manifest locale JSON, i18n message groups, locale resolution, generated i18n scripts, supported locales, translation wording, or dev locale override behavior. |
I18n v1 covers:
I18n v1 does not cover:
Supported locales are exactly:
en
zh_CN
ja
All other Stream Deck languages fall back to en.
PI messages live in packages/hub/src/i18n/message-groups/*.ts.
Do:
{ en, zh_CN, ja }.LocalizedMessage = Record<HubLocale, string> semantics; all locale
fields are required.const { t } = useI18n() and call t(message, values?).packages/hub/src/i18n/messages.ts as the barrel plus messageGroups
registry only.Do not:
messageCatalog plus remap layer.intl-messageformat unless a real plural/select requirement exists and
the archived plan is updated first.packages/hub/scripts/i18n-check.mjs intentionally imports leaf
message-groups/*.ts files directly. Do not replace that with source-text
parsing of messages.ts.
Manifest/action localization is generated from
packages/hub/src/i18n/manifest-messages.ts.
Generated files:
packages/hub/com.ez.sho-metrics.sdPlugin/en.json
packages/hub/com.ez.sho-metrics.sdPlugin/zh_CN.json
packages/hub/com.ez.sho-metrics.sdPlugin/ja.json
Do not hand-edit generated locale JSON. Update the manifest catalog, then run:
npm.cmd run i18n:generate
npm.cmd run i18n:check
For i18n changes, run the narrowest useful set:
npm.cmd run i18n:check
npm.cmd run test:unit
npm.cmd run test:pi
Run npm.cmd run build when changing Rollup constants, generated locale files,
or anything packaging-facing. Run npm.cmd run lint before committing.
If a command fails only because Buf cannot access its AppData module lock, rerun the same command with the normal approval flow rather than changing code or scripts.