jetpack-compose-m3

Migrate Wear OS Jetpack Compose apps to Material3 with version-matched samples.

6.6k|388|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/android/skills --skill jetpack-compose-m3-android
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetpack-compose-m3
Source: https://github.com/android/skills/tree/main/wear/jetpack-compose-m3
Command: npx skills add https://github.com/android/skills --skill jetpack-compose-m3-android

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid migration mistakes and broken UI behavior when upgrading Wear OS apps to Jetpack Compose Material3 (M3).

Core Features & Use Cases

  • Version-safe upgrades: Select the latest stable Wear Compose Material3 version and align Kotlin/Compose compiler requirements to prevent incompatible build configurations.
  • Sample-driven refactors: Extract and read the official version-matched component samples before implementing any code changes, so parameter names, slots, tokens, and behaviors match reality.
  • Migration guidance from M2.5/Horologist: Follow structured mapping and checklist-based component guidance (e.g., scaffolding, lazy columns, transformed scrolling, theming, navigation expectations) to reduce regressions during migration.
  • Scenario fit: Use when creating new Wear OS Material3 projects, updating existing apps, or migrating from Material 2.5 and/or Horologist.

Quick Start

Ask your agent to migrate an existing Wear OS app from Wear Compose Material 2.5/Horologist to Wear Compose Material3 using the latest stable versions, and to extract and read the official component samples first before making any code changes.

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 my Wear OS app from Compose Material 2.5 to Material 3?

Migrating Wear OS Compose to Material 3 requires selecting the latest stable Wear Compose Material3 version and aligning Kotlin and Compose compiler requirements to prevent incompatible build configurations.

What is the safest way to update Wear OS Compose components to Material3?

The safest approach to Wear OS Material3 migration is sample-driven refactoring, which involves extracting and reading official version-matched component samples before implementing code changes to ensure parameter names, slots, and tokens match reality.

Can I migrate my Wear OS app from Horologist to Jetpack Compose Material3?

Yes, you can migrate from Horologist to Wear Compose Material3 using structured mapping and checklist-based component guidance for scaffolding, lazy columns, transformed scrolling, and theming to reduce regressions during the transition.

Why does my Wear OS Compose Material3 migration break UI behavior?

Broken UI behavior during Wear OS Compose Material3 migration often results from incompatible build configurations or mismatched component tokens, which you can prevent by enforcing strict version selection and validating parameter names against official samples.

Do I need to check Kotlin and Compose compiler compatibility for Wear OS Material3?

Yes, you must verify Kotlin and Compose compiler compatibility when upgrading to Wear Compose Material3 to prevent incompatible build configurations and ensure mandatory Gradle sync validation passes successfully.