rugged-gemini: Skill for Claude Code

Kotlin Idioms and Patterns

Kotlin rewards conciseness, null safety, and coroutine-based concurrency. Idiomatic Kotlin = safe, expressive, interop-aware.

Scope: Kotlin coding idioms. Test naming: GEMINI.md § Testing Strategy.

Null Safety

1. ? for nullable types — never platform types without annotation:

   fun findById(id: String): Task?  // explicitly nullable
   fun getById(id: String): Task    // guaranteed non-null — throws if not found
   

2. Prefer ?.let {} and ?: (Elvis) over null checks.

3. Never !! in production — use requireNotNull with a message.

Data Classes and Sealed Types

1. data class for DTOs and domain objects:

   data class CreateTaskRequest(val title: String, val priority: Priority)
   

2. sealed class/sealed interface for restricted hierarchies:

   sealed interface TaskResult {
       data class Success(val task: Task) : TaskResult
       data class NotFound(val id: String) : TaskResult
       data class ValidationError(val errors: List<String>) : TaskResult
   }
   

3. Exhaustive when with sealed types:

   when (result) {
       is TaskResult.Success -> ok(result.task)
       is TaskResult.NotFound -> notFound(result.id)
       is TaskResult.ValidationError -> badRequest(result.errors)
   }
   

Coroutines

1. Structured concurrency — coroutineScope, supervisorScope.
2. Never GlobalScope.launch — always scoped.
3. Flow for reactive streams:

   fun observeTasks(): Flow<List<Task>> = flow {
       while (currentCoroutineContext().isActive) {
           emit(storage.getAll())
           delay(5.seconds)
       }
   }
   

Naming

1. PascalCase for classes. camelCase for functions, properties.
2. No get/set prefixes — use properties.
3. Backtick function names only in tests: `should create task when valid`()

Testing

1. kotest or JUnit 5 + MockK:

   @Test
   fun `create task returns task when valid`() {
       val result = service.create("Test", Priority.HIGH)
       assertThat(result.title).isEqualTo("Test")
   }