Android Material 3 Compose

Step 1: Define the interface contract

1. DEFINE new app/screen | component | theme | adaptive layout | accessibility fix | Material 2 migration | visual regression | UI performance issue.
2. IDENTIFY target/compile/min SDK, Material3/Compose/Kotlin/AGP tuple, supported windows and postures, navigation pattern, content hierarchy, theme modes, dynamic-color policy, localization/RTL, accessibility behavior, state owner, experimental-API policy, and proof surface.
3. READ the current Material Android Compose page, Material3 release notes, and affected component guidance before choosing APIs. Prefer the latest stable library; adopt alpha/beta only for a named requirement.
4. PRESERVE the product's existing design tokens, navigation/state contract, resource names, analytics semantics, and supported configurations unless the request changes them.
5. ROUTE shared Android/iOS/desktop/web UI to compose-multiplatform, Kotlin/Gradle failures to kotlin-development or kotlin-gradle, and BLE diagnostic interfaces to android-ble-inspector.

Completion: platform/version matrix, visual hierarchy, states, window classes, accessibility contract, and verification surfaces are explicit.

Step 2: Inspect the Android project

RUN from the repository root:

python3 scripts/inspect-project.py --root . --json