How do I install the Kotlin API Design skill?

Run npx skillmds@latest add hi-manshu/kotlin-api-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kotlin API Design safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kotlin API Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kotlin API Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kotlin API Design?

hi-manshu (@hi-manshu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kotlin API Design by hi-manshu — Agent Skill

Name: Kotlin API Design
Author: hi-manshu

Kotlin API Design

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.

hi-manshu Updated Sep 17, 2026

File contents

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.

---name: kotlin-api-designdescription: 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.---# Kotlin API design## Core principlePlace behavior, types, and platform seams where their meaning is clearest tocallers; use the smallest public abstraction that preserves domain language andplatform independence.## Procedure1. Name the domain concept, its owning type or module, and the callers that need to depend on it.2. Choose function ownership before adding an extension, factory, helper, or service layer.3. Represent a single-field domain concept with the smallest type that preserves its semantic and interop contract.4. Keep shared code semantic; put native SDK and platform details behind an interface or a narrowly justified expect/actual boundary.5. Read the focused reference for every material API decision below.6. 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](references/functions.md) || Primitive obsession, one-field domain type, `@JvmInline value class`, data class, interop, or Compose stability | [Value classes](references/value-classes.md) || Source sets, platform services, native SDKs, files, sensors, permissions, Compose Multiplatform interop, or expect/actual | [Multiplatform boundaries](references/multiplatform-boundaries.md) || Branching and guard-condition shape | [Kotlin control flow](../kotlin-control-flow/SKILL.md) |## RED/GREEN agent scenarios1. RED adds an extension on `String` to hide repository behavior. GREEN gives the behavior a domain owner or service with a meaningful dependency boundary.2. Novel case: shared UI needs a platform permission service. GREEN preserves a semantic shared contract and places platform SDK calls at the native leaf.3. Counterexample: an internal helper has one obvious owning class. GREEN keeps it a member instead of extracting a factory or value type for ceremony.

Frequently asked questions