context-kmp_skill

This skill assists Kotlin Multiplatform development tasks by guiding shared module creation, expect/actual usage, and Koin/SQLDelight/Ktor setup.
  • Shell

0

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill shotaiuchi/dotclaude --skill context-kmp

  • SKILL.md1.5 KB

Overview

This skill provides a focused Kotlin Multiplatform (KMP) development context to apply when working on shared modules, expect/actual declarations, and multiplatform UI. It guides usage patterns for common KMP libraries like Koin, SQLDelight, Ktor, and Compose Multiplatform. Use it to keep architecture, testing, and Kotlin conventions consistent across targets.

How this skill works

When enabled, the skill inspects project layout for shared/, commonMain/, and .kt files inside multiplatform modules and assumes expect/actual patterns are in play. It recommends layered architecture, dependency injection setup, multiplatform database and network patterns, and Compose Multiplatform UI approaches. It references established conventions and testing strategies to produce code and suggestions that fit KMP best practices.

When to use it

  • Creating or refactoring shared/ or commonMain/ modules
  • Designing or implementing expect/actual APIs across targets
  • Setting up or integrating Koin, SQLDelight, or Ktor in a multiplatform module
  • Building Compose Multiplatform screens and reusable UI components
  • Writing tests that target commonMain or multiple platforms

Best practices

  • Keep platform-specific code minimal and behind expect/actual boundaries
  • Follow clean architecture layers: domain, data, and presentation in shared code
  • Configure Koin modules in commonMain where possible and provide platform modules via actual
  • Use SQLDelight with multiplatform drivers and abstract database APIs in commonMain
  • Prefer suspend coroutines in shared APIs and expose Flow/SharedFlow for streams
  • Write tests for common behavior in commonTest and platform-specific tests separately

Example use cases

  • Create an expect interface for file I/O and implement actuals for Android and iOS
  • Set up a shared Ktor HttpClient with platform-specific engines via expect/actual
  • Define a shared SQLDelight database schema and provide platform drivers in actual modules
  • Register shared use-cases and repositories in a Koin module declared in commonMain
  • Build cross-platform UI components with Compose Multiplatform and share business logic

FAQ

Use expect/actual when behavior must differ by platform but share an API; use platform modules when entire implementations and dependencies are large or platform-only.

Where should dependency injection configuration live?

Declare DI bindings for shared abstractions in commonMain and provide platform-specific bindings (drivers, clients) via actual implementations or platform modules.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational