kotlin-ui-compose-multiplatform

Design and review shared Compose Multiplatform UI with state-driven architecture.

63|6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mmiani/kotlin-kmp-claude-agent-skills --skill kotlin-ui-compose-multiplatform-mmiani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-ui-compose-multiplatform
Source: https://github.com/mmiani/kotlin-kmp-claude-agent-skills/tree/main/skills/kotlin-ui-compose-multiplatform
Command: npx skills add https://github.com/mmiani/kotlin-kmp-claude-agent-skills --skill kotlin-ui-compose-multiplatform-mmiani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design and review a shared Compose Multiplatform UI, enforcing a state-driven architecture, clean composable boundaries, and a clear separation between common UI and platform-specific startup concerns.

Core Features & Use Cases

  • Guidance for building declarative, state-driven shared UI that can be compiled against commonMain with platform-specific bootstrapping kept separate.
  • Emphasis on composable decomposition, layout discipline, and explicit modifiers to improve readability and maintainability.
  • Support for adaptive UI considerations and previewability to accelerate iteration and cross-target consistency.
  • Accessibility and semantics considerations baked into the shared UI design.

Quick Start

Design and review a shared Compose Multiplatform UI using strict state-driven principles across common and platform-specific layers.

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 Compose Multiplatform UI for Android and iOS?

Structure shared Compose Multiplatform UI using strict state-driven principles in commonMain, keeping platform-specific bootstrapping separate to ensure clean composable boundaries and cross-platform consistency.

What's the best way to manage state in a shared Compose Multiplatform UI?

Manage state by enforcing a state-driven architecture with explicit composable decomposition and clear modifier boundaries, ensuring declarative UI logic remains previewable and maintainable across shared code.

How do I separate shared UI code from platform-specific startup in Kotlin Multiplatform?

Separate shared UI from platform-specific startup by isolating declarative composable logic in commonMain while deferring Android and iOS bootstrapping to their respective platform source sets.

Can I design adaptive layouts that work across Android and iOS in common code?

Yes, you can design adaptive layouts in common code by applying layout discipline, explicit modifiers, and accessibility semantics to ensure cross-target consistency and improve previewability during iteration.

Does this approach support accessibility and semantics in shared UI components?

Yes, shared UI components support accessibility and semantics by baking semantic considerations directly into the composable design within commonMain, ensuring inclusive behavior across Android and iOS targets.

When should I not use a shared Compose Multiplatform UI layer?

Avoid a shared Compose Multiplatform UI layer when platform-specific behaviors require deeply divergent startup logic or native UI components that cannot be cleanly abstracted through state-driven composable boundaries.