What problem does it solve? Writing Compose UI involves subtle pitfalls — recomposition storms, modifier ordering bugs, misused side effects, and deprecated APIs — that are hard to diagnose without deep knowledge of the Compose runtime and source code. ## Core Features & Use Cases - Topic-specific references: Covers state management, side effects, modifiers, navigation, animations, theming, accessibility, performance, focus/TV input, and production crash patterns. - Compose Multiplatform support: Guidance for Android, Desktop, iOS, and Web targets including expect/actual, resources, and platform-specific APIs. - Design-to-code workflow: Decomposes Figma frames or screenshots into composable trees with design-token mapping to MaterialTheme. - Source verification: Verifies behavior against live androidx/androidx and JetBrains compose-multiplatform-core source via MCP tools or raw GitHub. - Use Case: When a user says "my compose screen is slow" or "implement this design", the skill consults the relevant reference, flags anti-patterns, and produces minimal correct code. ## Quick Start Ask the assistant to review or build a Compose screen, for example: "Build this Figma card design in Compose and check my LazyColumn for recomposition issues."