kotlin-api-design

Original：🇺🇸 English

Translated

Use when designing or reviewing Kotlin function ownership, member or extension functions, factories, single-field domain types, value classes, data classes, Kotlin Multiplatform expect/actual declarations, or platform service boundaries.

4installs

Sourcechrisbanes/skills

Added on2026-08-13

NPX Install

npx skill4agent add chrisbanes/skills kotlin-api-design

SKILL.md Content

View Translation Comparison →

Kotlin API design

Core principle

Place behavior, types, and platform seams where their meaning is clearest to callers; use the smallest public abstraction that preserves domain language and platform independence.

Procedure

Name the domain concept, its owning type or module, and the callers that need to depend on it.
Choose function ownership before adding an extension, factory, helper, or service layer.
Represent a single-field domain concept with the smallest type that preserves its semantic and interop contract.
Keep shared code semantic; put native SDK and platform details behind an interface or a narrowly justified expect/actual boundary.
Read the focused reference for every material API decision below.
Finish when the public surface states domain intent, platform details remain at leaves, and callers do not depend on convenience abstractions with no clear owner.

Topic router

Signal	Read
Member vs top-level, extension, factory, service, or receiver choice	Function ownership
Primitive obsession, one-field domain type, `@JvmInline value class` , data class, interop, or Compose stability	Value classes
Source sets, platform services, native SDKs, files, sensors, permissions, Compose Multiplatform interop, or expect/actual	Multiplatform boundaries
Branching and guard-condition shape	Kotlin control flow

RED/GREEN agent scenarios

RED adds an extension on
```
String
```
to hide repository behavior. GREEN gives the behavior a domain owner or service with a meaningful dependency boundary.
Novel case: shared UI needs a platform permission service. GREEN preserves a semantic shared contract and places platform SDK calls at the native leaf.
Counterexample: an internal helper has one obvious owning class. GREEN keeps it a member instead of extracting a factory or value type for ceremony.