jetpack-compose-m3

Migrate Wear OS Compose UI from Material 2.5 or Horologist to Material3.

Updated May 22, 2026
One-click install
npx skills add https://github.com/ekawijayasusilo/kmp_template --skill jetpack-compose-m3-ekawijayasusilo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetpack-compose-m3
Source: https://github.com/ekawijayasusilo/kmp_template/tree/main/.claude/skills/jetpack-compose-m3
Command: npx skills add https://github.com/ekawijayasusilo/kmp_template --skill jetpack-compose-m3-ekawijayasusilo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Wear OS apps often break or look inconsistent when upgrading from older Compose Material (e.g., Material 2.5) to Material3, especially across components, theming, and layout behaviors.

Core Features & Use Cases

  • Version-safe upgrade planning: Determine the latest stable Wear Compose Material3 version and enforce required Kotlin/Compose compiler compatibility (including minSdk guidance).
  • Component migration with guardrails: Apply the recommended migration approach while avoiding unsupported mixed Material libraries and legacy Horologist composables.
  • Authoritative component behavior via extracted samples: Require extracting and reading the official <artifact>-<version>-samples-sources.jar samples before implementing any code changes.
  • Practical component checklist: Ensure correct usage patterns for key Wear components like AppScaffold, ScreenScaffold, and TransformingLazyColumn (including required modifiers and scroll behaviors).

Quick Start

Use the jetpack-compose-m3 skill to migrate your Wear OS Compose UI to Material3 by updating versions, extracting the official component samples for the resolved Material3 version, and then refactoring components according to the migration guide and checklist.

Frequently Asked Questions about jetpack-compose-m3

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

FAQPage Schema
How do I migrate Wear OS Compose to Material3 without breaking the UI?

To migrate Wear OS Compose to Material3 safely, you must resolve the latest stable version from Maven metadata, enforce Kotlin 2.0.0+ and Compose plugin compatibility, and extract the official version-matched samples before refactoring components.

What is the correct way to refactor AppScaffold and ScreenScaffold for Wear OS Material3?

Refactoring AppScaffold and ScreenScaffold requires extracting and reading the official artifact sample sources to enforce correct usage patterns, avoiding unsupported mixed Material libraries and legacy Horologist composables during the Material3 transition.

How does TransformingLazyColumn migration work when upgrading Wear Compose?

TransformingLazyColumn migration works by extracting the version-matched component samples to verify required modifiers and scroll behaviors, ensuring the layout remains consistent when upgrading to the Wear Compose Material3 library.

Do I need Kotlin 2.0.0 to use androidx.wear.compose.material3?

Yes, you need Kotlin 2.0.0 or higher and the correct Compose compiler plugin to use androidx.wear.compose.material3, as the migration enforces strict compatibility constraints to prevent runtime inconsistencies.

Why does my Wear OS Compose UI look inconsistent after moving to Material3?

Wear OS Compose UI looks inconsistent after moving to Material3 due to mixing legacy Horologist composables with new Material3 components, which requires applying version-safe upgrade planning and reading extracted official samples to fix.

Can I use navigation3 with Wear OS Compose Material3 components?

Yes, you can upgrade androidx.wear.compose.navigation3 usage alongside Material3, provided you resolve versions from Maven metadata and apply the recommended migration approach to avoid unsupported mixed Material libraries.