We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

• 0

  Common

  Most of the 10 edited versions we read keep these.

• 4

  Distinctive

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   When the user's task maps to a sub-skill above, read that sub-skill's SKILL.md before writing any code:

   line 49
2. Distinctive:

   If the task spans multiple sub-skills (e.g., Compose + Navigation), load both.

   line 56
3. Distinctive:

   Always check the sub-skill's Requirements and Verification sections before starting.

   line 60
4. Distinctive:

   Prefer Kotlin over Java for all new code.

   line 61
5. Distinctive:

   Follow the Modern Android Development guidance.

   line 62
6. Very specific:

   Use Gradle version catalog (libs.versions.toml) for dependency management.

   line 63
7. Very specific:

   Never run ./gradlew clean unless specifically required — it wastes build time.

   line 64

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.