Write idiomatic Kotlin
Use data and sealed types, null safety, collections, extension functions, delegation, generics, DSLs, and scope functions without obscuring behavior.
Codex Skills for Kotlin give Codex a practical workflow for writing idiomatic Kotlin, managing Gradle projects, modeling nullability, using coroutines safely, testing behavior, and working across backend, Android, multiplatform, and library code. Download the skills for Kotlin that remains clear at Java boundaries and predictable under concurrency.
task: complete kotlin development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong Kotlin code uses the type system deliberately, chooses simple language features, makes coroutine lifetime visible, and follows the project's compiler and library versions.
These skills guide Codex through modules, source sets, Gradle configuration, generated code, platform targets, tests, and interoperability before implementation.
Use data and sealed types, null safety, collections, extension functions, delegation, generics, DSLs, and scope functions without obscuring behavior.
Define structured concurrency, scopes, dispatchers, cancellation, exceptions, flows, channels, backpressure, and testable time behavior.
Work on JVM backends, Android, Kotlin Multiplatform, command-line tools, libraries, and Java interoperability.
Run Gradle tasks, compilation, unit and integration tests, static analysis, formatting, coroutine tests, and platform-specific checks.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read compiler and Gradle versions, modules, source sets, targets, dependencies, generated code, Java boundaries, tests, and style rules.
Follow nullability, state, exceptions, scopes, dispatchers, flows, resources, lifecycle, and serialization before changing behavior.
Prefer direct types and functions, preserve binary or API promises, keep coroutine lifetime structured, and match project conventions.
Compile affected targets, run tests and static analysis, check Java interop, exercise cancellation and errors, and validate generated output.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build APIs, persistence, serialization, authentication, coroutines, workers, configuration, logging, and tests.
Develop domain and data layers, ViewModels, flows, lifecycle-aware concurrency, tests, and shared modules.
Organize common and platform source sets, expect and actual declarations, shared logic, platform APIs, and target builds.
Design stable APIs, builders, extensions, generics, Java-friendly surfaces, documentation, tests, and releases.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable kotlin development work with a visible process.
Build maintainable features with deliberate types, concurrency, tests, and project conventions.
Use Kotlin and coroutines across lifecycle, data, domain, background, and shared application layers.
Develop Kotlin services with clear APIs, persistence, structured concurrency, and operational behavior.
Create stable Kotlin-first APIs that remain usable from Java and across supported targets.
The skills assist Kotlin development but do not replace platform-specific review, Android device testing, concurrency stress testing, compatibility checks, or validation against the declared compiler and dependency versions.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with language, coroutine, Gradle, interoperability, testing, and multiplatform guidance.
Install with the Kotlin repository so the workflow follows its compiler, modules, source sets, and targets.
Provide Kotlin and Gradle versions, JDK, targets, frameworks, coroutine libraries, generated code, API promises, and formatting rules.
Add compile, test, static-analysis, formatting, Android, multiplatform, integration, benchmark, and publication tasks.
Practical answers about capabilities, limits, setup, and review.
Yes. They emphasize structured concurrency, ownership, cancellation, dispatchers, exceptions, flows, backpressure, and testability.
Yes. They can handle Kotlin application layers while respecting Android lifecycle, Gradle, device, and framework constraints.
Yes, when the target platforms, source sets, versions, and expected platform behavior are provided.
Yes. They can review nullability, overloads, names, defaults, functional interfaces, exceptions, and generated JVM signatures.
The workflow follows current project conventions and favors clarity over using language features merely because they are concise.
Clear context. Purposeful work. Relevant checks. A result others can understand.