Skill
android-benchmark-comp…
Use when comparing physical Android benchmark configurations, investigating inconsistent rankings, or selecting an Android default from measured results. Do…
@chrisbanesView SkillDevelopment
Skill
/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.
Install
$ npx -y skills add chrisbanes/skills --skill kotlin-api-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/kotlin-api-design
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
kotlin-api-design.SKILL.mdname: kotlin-api-design
description: 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 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
1. 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. When reviewing a public mapping over a sealed result, name every caller-visible outcome. Flag a catch-all `else` that hides a subtype and recommend explicit subtype branches so the contract stays exhaustive and preserves smart casts. 4. Represent a single-field domain concept with the smallest type that preserves its semantic and interop contract. 5. Keep shared code semantic; put native SDK and platform details behind an interface or a narrowly justified expect/actual boundary. 6. Read the focused reference for the selected decision below. 7. 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, guard-condition shape, sealed-result mapping, or a catch-all `else` | [Kotlin control flow](../kotlin-control-flow/SKILL.md) |
Read more
name: kotlin-api-design description: 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 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
1. 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. When reviewing a public mapping over a sealed result, name every caller-visible outcome. Flag a catch-all `else` that hides a subtype and recommend explicit subtype branches so the contract stays exhaustive and preserves smart casts. 4. Represent a single-field domain concept with the smallest type that preserves its semantic and interop contract. 5. Keep shared code semantic; put native SDK and platform details behind an interface or a narrowly justified expect/actual boundary. 6. Read the focused reference for the selected decision below. 7. 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, guard-condition shape, sealed-result mapping, or a catch-all `else` | [Kotlin control flow](../kotlin-control-flow/SKILL.md) |
Ships withchrisbanes-skills
A set of skills for Kotlin, Jetpack Compose, Android development, and grounded writing. The repository is also a portable Agent Plugins and the immediate skill directories under skills/.
Get the whole plugin
Stats
1,041
Stars
50
Forks
Active
Maintenance
Python
Language
Apache-2.0
License
5d ago
Last commit
4mo ago
Created
Repo: chrisbanes/skills
Other skills on chrisbanes-skills.
@chrisbanesView SkillSkill
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple…
@chrisbanesView SkillSkill
compose-component-desi…
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content,…
@chrisbanesView SkillSkill
compose-focus-navigati…
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events,…
@chrisbanesView SkillSkill
compose-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase…
@chrisbanesView SkillSkill
compose-state-and-effe…
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect,…
@chrisbanesView Skill