What problem does it solve? Adding localization keys to an ASP.NET Zero project is error-prone because duplicate keys cause ABP to throw an AbpException at runtime, and developers often recreate keys that already exist. This Skill provides the conventions, search commands, and standard key patterns needed to add translations safely across all language XML files. ## Core Features & Use Cases - Duplicate Prevention: Provides PowerShell search commands to verify a key does not already exist before adding it, avoiding AbpException crashes. - Standard Key Conventions: Defines the canonical key set per feature (CreateNew{Feature}, Edit{Feature}, {Feature}DeleteWarningMessage) plus a list of existing common keys to reuse. - Usage Patterns: Shows how to consume localized strings in C# app services via L(), in Angular templates via the localize pipe, and in TypeScript via this.l(). - Use Case: When adding a new Products feature, generate the full set of PascalCase localization keys with {0} placeholders in CadentManagement.xml and its translated variants without duplicating existing entries. ## Quick Start Add localization keys for a new Products feature to the ASP.NET Zero XML files following the standard conventions.
