djkovrik

Write or update unit tests for Decompose components in the Tackle Kotlin Multiplatform project. Use when testing component models, child navigation, child item creation, ComponentOutput propagation, lifecycle cleanup, or component method wiring.

Create or update Decompose components and navigation in the Tackle Kotlin Multiplatform project. Use when adding a new screen/component, wiring component gateways, adding child stacks/slots/items, connecting a component to Compose UI, or propagating ComponentOutput events.

Create or update MVIKotlin stores in the Tackle Kotlin Multiplatform project. Use when adding a new component store, changing store intents/state/labels, wiring a domain manager into a store, or adapting store state to a Decompose component model.

Write or update unit tests for MVIKotlin stores in the Tackle Kotlin Multiplatform project. Use when testing store bootstrap, intents, reducer state, labels, error labels, optimistic updates, or pagination behavior.

Write or update non-component unit tests in the Tackle Kotlin Multiplatform project. Use when testing domain managers, mappers, utilities, database behavior, settings wrappers, network response mapping, or other commonTest code that is not a MVIKotlin store or Decompose component.

Use in the Blinkly Kotlin Multiplatform repository when writing, updating, or reviewing commonTest coverage for Decompose components, including child stack navigation, onboarding flow transitions, home tab navigation, parent-child `ComponentOutput` propagation, Store-backed component models, lifecycle handling, coroutine side effects, and Mokkery-based collaborator verification.

Use in the Blinkly Kotlin Multiplatform repository when adding, changing, or reviewing Decompose component contracts, default implementations, factories, navigation stacks, child outputs, tab navigation, or Compose bindings to Decompose `Value`, `ChildStack`, and component models under `shared/component/**` or `shared/compose/**`.

Use in the Blinkly Kotlin Multiplatform repository when adding, changing, or reviewing MVIKotlin Store contracts, StoreProviders, reducers, coroutine executors, bootstrappers, labels, integration mappers, or Store-backed component models under `shared/component/**`; prefer this over generic MVIKotlin guidance whenever a Blinkly component may need reducer-owned state, startup work, subscriptions, async business logic, or one-off errors.