Migrate custom Jetpack Compose components and theming to the Experimental Styles API.
npx skills add https://github.com/android/skills --skill styles-android
Please help me install this Agent Skill. Skill: styles Source: https://github.com/android/skills/tree/main/jetpack-compose/theming/styles Command: npx skills add https://github.com/android/skills --skill styles-android
Jetpack Compose theming often relies on scattered hard-coded styling and modifier-heavy patterns that are hard to unify across components, so it becomes difficult to migrate a design system to a consistent, theme-driven approach.
ComponentStyles.kt, expose it through your custom theme, and access theme tokens from StyleScope.style: Style parameter or apply styling via Modifier.styleable(), including state-based interaction styling using StyleState.Tell your AI to migrate your custom Jetpack Compose button from hard-coded parameters to a shared ComponentStyles.kt Style that supports enabled/pressed/hovered styling.
High-intent search queries and answers about installing and using this skill.
Migrating Jetpack Compose components to the Styles API involves replacing hard-coded styling by creating a central ComponentStyles module, exposing it through your theme, and updating components to accept a Style parameter or apply Modifier.styleable with StyleState tracking.
Unifying hard-coded styling in Jetpack Compose theming is achieved by migrating to a theme-driven approach using the experimental Styles API, which replaces scattered modifiers with a central ComponentStyles layer exposed via your custom theme.
Handling state-based interaction styling with Modifier.styleable in Compose requires tracking component states like enabled, pressed, or hovered using StyleState to apply the correct style tokens from your ComponentStyles layer.
Yes, using the Jetpack Compose Styles API requires experimental opt-in and meeting specific compile and Compose Foundation version dependencies to access the experimental Styles APIs for your custom components.
The Compose Styles API migration workflow skips unsupported Material Design component Styles, targeting custom UI components and custom themes to wire Style tokens into a component-wide theming layer instead.
ComponentStyles integrates with a custom Jetpack Compose theme by creating a central ComponentStyles.kt file, exposing it through your theme provider, and allowing components to access theme tokens directly from StyleScope.
premex-abMigrate Jetpack Compose components to theme-driven Style definitions.
klxiaoniuMigrate Jetpack Compose UIs to themeable Styles with StyleState.
fornewidMigrate Jetpack Compose custom component styling to the experimental Styles API.
shirulotIntegrate Jetpack Compose Styles API into Android projects for centralized styling.