Run any Skill in Manus with one click

localization

Stars2

Forks0

UpdatedJune 19, 2026 at 06:50

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.

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.

Run Skill in Manus

Source

Not-Endurance

Not-Endurance/not-timing-system

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

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.

NTS Localization

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.

Key Ownership

Add generic/shared keys to NStrings.
Add NTS-specific component or application wording to NtsStrings.
Keep UI code and Razor markup referencing the strongly typed string property instead of raw resource key literals.

Key Naming

Name the property after the English text itself, not after where it is used.
Use snake case: spaces become underscores.
Represent dynamic values in the property name with a double underscore.
Always end localized string properties with _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));

Resources

Add every new key to src/NTS/Localization/Resources/LocalizedStrings.resx with the English value as the default.
Add translations for the same key to the other supported resource files, currently LocalizedStrings.bg.resx and LocalizedStrings.tr.resx.
When only part of a value is dynamic, use a placeholder in the resource value and surround it with single quotes, for example Cannot delete '{0}' because it is used.

Blazor Usage

In Blazor behind classes, expose localized text through protected properties only when markup needs extra state, composition, formatting, or fallback logic.
Do not propagate simple localized text through unnecessary behind properties; use NStrings or NtsStrings directly in Razor when no extra state or composition is needed.
Keep injected/default-access properties first, protected members next, and public [Parameter]/[CascadingParameter] properties last to satisfy the static analyzer ordering rules.

More from this repository

same repository

solid

Not-Endurance/not-timing-system

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.

2026-06-232

writing-great-skills

Not-Endurance/not-timing-system

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

2026-06-202

code-style

Not-Endurance/not-timing-system

Use when adding, reviewing, or refactoring NTS C# or Razor code where member ordering, property ordering, analyzer sorting, or formatting decisions matter.

2026-06-192

service-injection

Not-Endurance/not-timing-system

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.

2026-06-192

user-facing-text

Not-Endurance/not-timing-system

Use when adding or changing user-facing text in NTS UI, contracts, validation messages, resources, helper text, labels, buttons, or localized strings.

2026-06-192

blazor-components

Not-Endurance/not-timing-system

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.

2026-06-032

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.

NTS Localization

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.

Key Ownership

Add generic/shared keys to NStrings.
Add NTS-specific component or application wording to NtsStrings.
Keep UI code and Razor markup referencing the strongly typed string property instead of raw resource key literals.

Key Naming

Name the property after the English text itself, not after where it is used.
Use snake case: spaces become underscores.
Represent dynamic values in the property name with a double underscore.
Always end localized string properties with _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));

Resources

Add every new key to src/NTS/Localization/Resources/LocalizedStrings.resx with the English value as the default.
Add translations for the same key to the other supported resource files, currently LocalizedStrings.bg.resx and LocalizedStrings.tr.resx.
When only part of a value is dynamic, use a placeholder in the resource value and surround it with single quotes, for example Cannot delete '{0}' because it is used.

Blazor Usage

In Blazor behind classes, expose localized text through protected properties only when markup needs extra state, composition, formatting, or fallback logic.
Do not propagate simple localized text through unnecessary behind properties; use NStrings or NtsStrings directly in Razor when no extra state or composition is needed.
Keep injected/default-access properties first, protected members next, and public [Parameter]/[CascadingParameter] properties last to satisfy the static analyzer ordering rules.