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. Distinctive:

   When writing Kotlin, leverage its modern, expressive syntax and safety features:

   line 11
2. Very specific:

   Immutability: Prefer val over var for variable declarations, and use immutable collections (List, Map) unless mutation is explicitly …

   line 13
3. Very specific:

   Null Safety: Avoid the !! operator. Use safe calls ?., the Elvis operator ?:, or let blocks to handle nullable types.

   line 14
4. Very specific:

   Coroutines: Use coroutines (suspend functions, launch, async) for asynchronous operations instead of raw threads or callbacks.

   line 15
5. Very specific:

   Data Classes: Use data class for models and DTOs to automatically generate equals(), hashCode(), and copy().

   line 16
6. Distinctive:

   Extension Functions: Use extension functions to add utility methods to existing classes without subclassing, keeping the core APIs clean.

   line 17

≈ “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.