What problem does it solve?
Adopting Jetpack Compose Styles reduces repeated styling and enables consistent, theme-driven UI—but migration is non-trivial and requires careful dependency, compiler, and code refactoring.
Core Features & Use Cases
- Dependency and API enablement: Guides you through required Compose versions and the exact Styles API import (
androidx.compose.foundation.style.Style), including experimental API opt-in.
- Theme-first migration: Shows how to structure component styles (via a
ComponentStyles.kt file) and connect them to custom themes for design-token-driven styling.
- Component refactor workflow: Provides an end-to-end approach to replace hard-coded styling parameters with a
style: Style parameter and apply Modifier.styleable() with state tracking using StyleState for interaction states.
- Validation strategy: Recommends build checks plus screenshot-based visual parity validation (where possible) to prevent regressions.
Quick Start
Use the styles skill to migrate a custom design system component in your Jetpack Compose project to use the Styles API and stateful Modifier.styleable() styling.