メニュー
Use when adding, reviewing, or refactoring NTS localized user-facing text, NStrings/NtsStrings properties, localized resource values, placeholders, translations, or deciding whether text should be localized.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | localization |
| description | Use when adding, reviewing, or refactoring NTS localized user-facing text, NStrings/NtsStrings properties, localized resource values, placeholders, translations, or deciding whether text should be localized. |
Use localization for text intended to be seen by end users. Do not localize developer-only diagnostics such as GuardHelper messages or similar internal invariant/helper errors.
NStrings.NtsStrings._string.Examples:
public static string Home_string => LocalizeString(nameof(Home_string));
public static string Sorry_we_seem_to_have_fallen_off_the_horseback_string =>
LocalizeString(nameof(Sorry_we_seem_to_have_fallen_off_the_horseback_string));
public static string Cannot_delete___because_it_is_used_string =>
LocalizeString(nameof(Cannot_delete___because_it_is_used_string));
src/NTS/Localization/Resources/LocalizedStrings.resx with the English value as the default.LocalizedStrings.bg.resx and LocalizedStrings.tr.resx.Cannot delete '{0}' because it is used.NStrings or NtsStrings directly in Razor when no extra state or composition is needed.[Parameter]/[CascadingParameter] properties last to satisfy the static analyzer ordering rules.Use when adding, reviewing, or refactoring object-oriented or service-oriented code where SOLID design, dependency boundaries, class/interface responsibilities, polymorphism, abstraction, or maintainability tradeoffs matter. Apply the SOLID principles through a practical lens: improve cohesion, substitutability, and dependency direction without adding abstraction ceremony that the current code does not need.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Use when adding, reviewing, or refactoring NTS C# or Razor code where member ordering, property ordering, analyzer sorting, or formatting decisions matter.
Use when adding, reviewing, or refactoring dependency injection registrations, service abstractions, state contexts, injected collaborators, IServiceCollection extension methods, or service/processor/context interface naming in NTS and Not packages.
Use when adding or changing user-facing text in NTS UI, contracts, validation messages, resources, helper text, labels, buttons, or localized strings.
Use when adding, reviewing, or refactoring NTS Blazor/Razor components, especially .razor files, component parameters, injected services, event callbacks, print components, or UI code-behind classes that should follow the repo's split .razor plus Behind.cs convention.