jetpack-compose-m3

Name: jetpack-compose-m3
Availability: InStock
Author: shirulot

Migrate Wear OS apps to Material 3 using androidx.wear.compose.material3.

Updated Jul 6, 2026

Search Tags:#migration #android #kotlin #compose #material3 #wear os

Ready to run

npx skills add https://github.com/shirulot/codex-skill --skill jetpack-compose-m3-shirulot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jetpack-compose-m3
Source: https://github.com/shirulot/codex-skill/tree/main/jetpack-compose-m3
Command: npx skills add https://github.com/shirulot/codex-skill --skill jetpack-compose-m3-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of migrating Wear OS applications to Material3 Expressive, ensuring developers follow strict architectural patterns and avoid deprecated libraries like Horologist or Material 2.5.

Core Features & Use Cases

Migration Guidance: Provides a structured path for transitioning from M2.5 to M3, including component mapping and theme updates.
Component Best Practices: Enforces the use of modern components like TransformingLazyColumn and AppScaffold over legacy alternatives.
Sample-Driven Development: Mandates the extraction and use of official component samples to ensure implementation accuracy and adherence to design tokens.

Quick Start

Use the jetpack-compose-m3 skill to guide the migration of my current Wear OS project to Material3 Expressive.

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 a Wear OS application from Material 2.5 to Material 3?▼

Migrating Wear OS to Material 3 involves following a structured path from M2.5 to M3, enforcing component mappings, updating theme configurations, and replacing deprecated libraries with modern components like AppScaffold.

What Wear OS components should replace deprecated Material 2.5 layouts?▼

Replace deprecated M2.5 layouts with modern Wear OS components like TransformingLazyColumn and AppScaffold to ensure technical compliance with modern architectural standards and avoid legacy libraries.

Can I use Horologist libraries for my Wear OS Material 3 development?▼

Avoid using Horologist libraries for Wear OS Material 3 development. The migration enforces strict architectural patterns by mandating modern component extraction and adherence to current design tokens instead of deprecated alternatives.

What is the best way to ensure accurate Wear OS Material 3 component implementation?▼

The best way to ensure accurate Wear OS Material 3 implementation is sample-driven development, mandating the extraction of official component samples to guarantee adherence to design tokens and modern architectural standards.

Why does my Wear OS Material 3 migration require design token adherence?▼

Wear OS Material 3 migration requires design token adherence to ensure technical compliance with Material3 Expressive standards and maintain consistency with official component samples during the transition from legacy architectures.