kotlin-flow-state-event-modeling

What problem does it solve?

It solves the common Kotlin Flow mistakes that cause lost one-shot events, stale UI state, and unsafe state initialization that leaks placeholder/sentinel domain values into the app.

Core Features & Use Cases

• Correctly model UI state vs one-shot events: Use StateFlow for always-available state and Buffered Channel/receiveAsFlow for exactly-once navigation/snackbar events.
• Avoid concurrency bugs in MutableStateFlow: Prefer MutableStateFlow.update to prevent lost updates from read-modify-write patterns.
• Prevent inefficient or incorrect sharing: Ensure stateIn is defined once (as a val) and choose SharingStarted.WhileSubscribed only when stale cached .value is acceptable.
• Keep synchronous access when deriving state: Don’t rely on .map over StateFlow when consumers need synchronous .value; terminate with .stateIn.

Quick Start

Use the kotlin-flow-state-event-modeling skill to review a ViewModel’s StateFlow/SharedFlow/Channel design and identify where events may drop, where .value may go stale, or where update/stateIn decisions could cause concurrency or performance issues.