Localization Developer (Smart Router)

Prevent hardcoded strings by using `Loc` constants tied to keys stored in your .xcstrings files. This Skill guides you to add keys to the correct Auth, Workspace, or UI .xcstrings file, run `make generate` to produce Strings.swift, and reference the resulting `Loc` constant instead of embedding text directly in code.

Determine which .xcstrings file your string belongs to (Auth, Workspace, or UI), search for existing keys to avoid duplicates, add the new key, run `make generate` to create the Strings.swift file with `Loc` constants, then use that constant in your code.

Parameterized `Loc` constants handle dynamic text formatting without manual string manipulation. Define keys with placeholders in your .xcstrings files, run `make generate`, and use the resulting `Loc` constant with parameters to safely inject values into localized strings.

Separating strings into Auth, Workspace, and UI .xcstrings files reduces merge conflicts, improves maintainability, and prevents duplicate keys across your localization structure. This organization makes it easier to locate and update related strings.

Yes. This Skill structures localization for authentication strings (Auth .xcstrings), collaboration and object management strings (Workspace .xcstrings), and general UI strings (UI .xcstrings), allowing you to organize translations by functional domain.

Duplicates create inconsistent translations and maintenance overhead. This Skill enforces searching for existing keys before adding new ones, ensuring each string is defined once and preventing translation conflicts across Auth, Workspace, and UI files.