string-resources-convention

What problem does it solve?

Prevents Android string resource bugs and localization regressions by enforcing a consistent naming scheme and mandatory translator comments for every touched resource block.

Core Features & Use Cases

• Standardized naming pattern: Ensures resources follow {prefix}_{module_or_context}_{specific_identifier} with approved prefixes like label_, title_, action_, error_, and others for clearer maintenance and discovery.
• Localization-ready formatting rules: Guides correct use of positional placeholders like %1$s / %2$d, formatted="true", and appropriate decisions for getText() vs getString().
• Mandatory POEditor translator context: Requires an XML comment immediately above each <string>, <plurals>, and <string-array> block so translators have intent, variables, and tone.

Quick Start

Use the string-resources-convention skill when adding or modifying strings.xml entries so the new resources follow the naming pattern and include translator comments for each resource block.