https://developer.android.com/agents/skills/wear/jetpack-compose-m3/skill

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

5|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/fornewid/android-developers-changelog --skill https-developer-android-com-agents-skills-wear-jetpack-compose-m3-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: https://developer.android.com/agents/skills/wear/jetpack-compose-m3/skill
Source: https://github.com/fornewid/android-developers-changelog/tree/main/docs/agents/skills/wear/jetpack-compose-m3
Command: npx skills add https://github.com/fornewid/android-developers-changelog --skill https-developer-android-com-agents-skills-wear-jetpack-compose-m3-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken Wear OS Compose Material3 implementations by enforcing correct library/Kotlin compatibility, version pinning, and sample-based parameter usage.

Core Features & Use Cases

  • Safe version selection and constraints: Determines the latest stable androidx.wear.compose:compose-material3 version (highest non-prerelease) and enforces Kotlin/Compose compiler requirements and minSdk >= 25.
  • Deterministic migration workflow: Applies Material3 migration guidance, avoids unsupported libraries (like Horologist), and validates component changes against canonical mappings.
  • Sample-first component correctness: Requires extraction and local reading of the official <artifact>-<version>-samples-sources.jar contents before any implementation, ensuring slot names, defaults, and behaviors match the exact library version.
  • Component checklist to avoid subtle UI/behavior regressions: Provides Wear-specific guidance (e.g., TransformingLazyColumn rules, AppScaffold/ScreenScaffold structure, overscroll handling for EdgeButton, typography/color usage).

Quick Start

Use this skill to migrate your Wear Compose project to Material3 by extracting and reading the version-matched component samples, then implementing the required components following the checklist guidance.

Frequently Asked Questions about https://developer.android.com/agents/skills/wear/jetpack-compose-m3/skill

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

FAQPage Schema
How do I migrate Wear OS Jetpack Compose to Material3 without breaking component behaviors?▼

Migrating Wear OS Compose to Material3 requires extracting version-matched official sample sources before coding, validating Gradle sync, and enforcing Kotlin/Compose compiler compatibility alongside minSdk >= 25 to prevent UI regressions.

What are the Kotlin and minSdk requirements for Wear Compose Material3?▼

Wear Compose Material3 mandates minSdk >= 25 and strict Kotlin/Compose compiler compatibility matching the highest non-prerelease androidx.wear.compose:compose-material3 version to maintain library stability.

How do I correctly implement TransformingLazyColumn and AppScaffold in Wear Compose M3?▼

Implementing TransformingLazyColumn and AppScaffold in Wear Compose M3 requires reading the official version-matched sample sources first, then applying specific checklist guidance for scaffolding structure and overscroll handling.

Why should I extract sample sources before implementing Wear Compose Material3 components?▼

Extracting official sample sources before implementing Wear Compose Material3 components ensures slot names, defaults, and behaviors match the exact library version, preventing subtle UI and behavior regressions.

What should I do if Gradle sync fails after resolving Wear Compose Material3 references?▼

If Gradle sync fails after resolving Wear Compose Material3 references, you must not guess fixes; instead, validate the Gradle sync and re-inspect the official version-matched sample sources for correct implementation.

Can I use Horologist libraries when migrating to Wear Compose Material3?▼

You cannot use Horologist libraries when migrating to Wear Compose Material3, as the deterministic migration workflow explicitly avoids unsupported libraries to ensure safe and correct component implementation.