kotlin-ui-compose-multiplatform

Enforce state-driven shared UI guidelines in Kotlin Multiplatform Compose commonMain code.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-ui-compose-multiplatform-leogallego
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-ui-compose-multiplatform
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/kotlin-ui-compose-multiplatform
Command: npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-ui-compose-multiplatform-leogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies best practices for designing, implementing, and reviewing shared UI in Kotlin Multiplatform Compose projects, ensuring a declarative, state-driven architecture and clean separation between shared UI and platform-specific startup concerns.

Core Features & Use Cases

  • Defines guidelines for state-driven UI, proper composable decomposition, and adaptive layout readiness across commonMain
  • Emphasizes previewability, structured window-size decisions, and deliberate modifier discipline
  • Serves as a reference for teams building cross-platform UI components that stay platform-agnostic while remaining easy to test and evolve

Quick Start

Structure shared UI in commonMain, hoist state appropriately, and enable previews for cross-platform targets.

Frequently Asked Questions about kotlin-ui-compose-multiplatform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure shared UI in Kotlin Multiplatform Compose to avoid platform-specific divergence?

Structure shared UI in commonMain by enforcing consistent state-driven architecture, composable decomposition, and deliberate modifier discipline. This approach improves maintainability and ensures Android, Desktop, and iOS targets remain platform-agnostic.

What's the best way to manage state ownership in Compose Multiplatform commonMain code?

Manage state ownership in Compose Multiplatform by hoisting state appropriately within commonMain code. Define clear component boundaries and state-driven requirements to ensure UI remains testable, previewable, and easy to evolve.

Can I use Compose Multiplatform shared UI for Android, Desktop, and iOS projects?

Yes, Compose Multiplatform shared UI applies to Android, Desktop, and iOS projects. It enforces a declarative, state-driven architecture with clean separation between shared UI components and platform-specific startup concerns.

How do I make Kotlin Multiplatform Compose components adaptive and previewable across platforms?

Make Kotlin Multiplatform Compose components adaptive and previewable by defining structured window-size decisions and enabling intuitive previews. This ensures cross-platform components maintain layout discipline and adaptive readiness.

Why does my shared Compose Multiplatform UI diverge between platforms?

Shared Compose Multiplatform UI diverges when teams lack consistent guidelines for state ownership, component boundaries, and modifier discipline. Codifying a state-driven architecture in commonMain prevents platform-specific fragmentation.

Does Kotlin Multiplatform Compose require separating shared UI from platform-specific startup logic?

Yes, Kotlin Multiplatform Compose requires a clean separation between shared UI in commonMain and platform-specific startup concerns. This declarative separation keeps cross-platform components platform-agnostic and testable.