What problem does it solve? Migrating custom Android design system components to the Jetpack Compose Styles API involves dependency upgrades, experimental compiler opt-ins, theme restructuring, and per-component refactoring that is easy to get wrong without a guided workflow. ## Core Features & Use Cases - Guided Migration Workflow: Step-by-step process covering dependency upgrades, compiler opt-in flags, ComponentStyles setup, and per-component conversion to Modifier.styleable. - State-Based Styling: Instructions for wiring MutableStyleState with interaction sources to handle pressed, hovered, focused, and disabled states, plus built-in animate blocks. - Theme Integration: Patterns for exposing component styles through a custom theme with StyleScope extensions that read CompositionLocal design tokens. - Use Case: You maintain a custom Compose design system with hardcoded styling parameters on components like CustomButton. Use this Skill to remove those parameters, centralize defaults in a ComponentStyles file, and validate visual parity with screenshot tests. ## Quick Start Migrate my CustomButton composable to use the Jetpack Compose Styles API with a style parameter and Modifier.styleable.