kotlin-multiplatform-compose-state-hoisting

When to Use This Skill

Use when you need to:

• Decide where state should live in a Compose component tree
• Make a composable testable and previewable by removing internal state
• Share state between sibling composables
• Understand why a component is hard to test (state is buried)
• Explain or implement "controlled" vs "uncontrolled" composable patterns

Trigger keywords: state hoisting, lift state, hoist state, stateful composable, stateless composable, controlled input, value onValueChange, where does state go, single source of truth, state sharing, Compose state management.

Freshness rule: Compose state management guidance tracks CMP releases — recheck the JetBrains CMP docs before upgrading or copying patterns into a new project.

Recommendation First