We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Read docs/translation-playbook.md and docs/localization.md completely.

   line 8
2. Distinctive:

   Use a fresh model context to critique meaning, naturalness, glossary consistency, and sensitive strings.

   line 17
3. Very specific:

   Add the locale to AppLanguage, the Appearance label map, picker-label resources, locales_config.xml, and AppLanguageTest.

   line 25
4. Very specific:

   Keep the registry at ai-translated until a fluent review PR is recorded.

   line 27
5. Very specific:

   Run the locale validator, both flavor compilations, and Android lint as documented in docs/localization.md.

   line 28
6. Distinctive:

   Keep one locale per commit.

   line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.