What problem does it solve? Hardcoded styling parameters scattered across custom Compose components make design systems hard to maintain and theme consistently. This Skill guides the migration of custom components to the Jetpack Compose Styles API, centralizing visual definitions into reusable, themeable Style objects. ## Core Features & Use Cases - Dependency and Compiler Setup: Upgrades Compose foundation dependencies and configures the opt-in compiler flag for the experimental Styles API. - Component Migration Workflow: Step-by-step process to remove hardcoded styling parameters, add a style: Style = Style parameter, wire MutableStyleState for interaction states, and apply Modifier.styleable. - Theme Integration: Establishes a ComponentStyles holder exposed through a custom theme, with StyleScope extensions for accessing design tokens. - Use Case: You maintain a custom design system like Jetsnack and want to replace per-component backgroundColor, shape, and textStyle parameters with unified Style definitions that support pressed, hovered, and disabled states with built-in animations. ## Quick Start Migrate my CustomButton composable to use the Jetpack Compose Styles API and move its hardcoded styling into a shared ComponentStyles file.