hub-i18n

Stars12

Forks0

UpdatedJune 16, 2026 at 04:01

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

ShoMetrics

ShoMetrics/sho_metrics

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

Scope

I18n v1 covers:

Stream Deck manifest and action-list copy.
Property Inspector UI copy.
Node/Hub user-visible copy shown in the Property Inspector.

I18n v1 does not cover:

Stored settings proto or global settings.
Deck key SVG text.
C# helper or Control Panel copy.
Logs or DEBUG raw diagnostic details.
Dynamic hardware, sensor, disk, or network-interface names.

Supported locales are exactly:

en
zh_CN
ja

All other Stream Deck languages fall back to en.

Message Catalog Rules

PI messages live in packages/hub/src/i18n/message-groups/*.ts.

Do:

Add user-visible PI strings to the owning domain message group.
Keep each message as { en, zh_CN, ja }.
Use LocalizedMessage = Record<HubLocale, string> semantics; all locale fields are required.
Import the narrow message group needed by the component.
Use const { t } = useI18n() and call t(message, values?).
Keep packages/hub/src/i18n/messages.ts as the barrel plus messageGroups registry only.

Do not:

Add a flat god catalog or hidden messageCatalog plus remap layer.
Hand-write string ids in application code.
Add stable generated ids for ordinary PI messages.
Add a source-text scanner for hard-coded strings.
Add intl-messageformat unless a real plural/select requirement exists and the archived plan is updated first.
Put translated strings into stored settings, proto, or renderer contracts.

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 Locale JSON

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

Validation

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.

More from this repository

same repository

logging

ShoMetrics/sho_metrics

Use when reading or writing any ShoMetrics log.

2026-06-2212

architecture-boundaries

ShoMetrics/sho_metrics

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.

2026-06-2012

coding-style

ShoMetrics/sho_metrics

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.

2026-06-1612

csharp-coding-style

ShoMetrics/sho_metrics

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.

2026-06-1612

naming-guidance

ShoMetrics/sho_metrics

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.

2026-06-1612

performance

ShoMetrics/sho_metrics

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.

2026-06-1612

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.

Scope

I18n v1 covers:

Stream Deck manifest and action-list copy.
Property Inspector UI copy.
Node/Hub user-visible copy shown in the Property Inspector.

I18n v1 does not cover:

Stored settings proto or global settings.
Deck key SVG text.
C# helper or Control Panel copy.
Logs or DEBUG raw diagnostic details.
Dynamic hardware, sensor, disk, or network-interface names.

Supported locales are exactly:

en
zh_CN
ja

All other Stream Deck languages fall back to en.

Message Catalog Rules

PI messages live in packages/hub/src/i18n/message-groups/*.ts.

Do:

Add user-visible PI strings to the owning domain message group.
Keep each message as { en, zh_CN, ja }.
Use LocalizedMessage = Record<HubLocale, string> semantics; all locale fields are required.
Import the narrow message group needed by the component.
Use const { t } = useI18n() and call t(message, values?).
Keep packages/hub/src/i18n/messages.ts as the barrel plus messageGroups registry only.

Do not:

Add a flat god catalog or hidden messageCatalog plus remap layer.
Hand-write string ids in application code.
Add stable generated ids for ordinary PI messages.
Add a source-text scanner for hard-coded strings.
Add intl-messageformat unless a real plural/select requirement exists and the archived plan is updated first.
Put translated strings into stored settings, proto, or renderer contracts.

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 Locale JSON

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

Validation

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.