Using chrisbanes skills

Core principle

Route by the decision the code needs, not by the number of APIs mentioned in the prompt. Load one cluster when its shared procedure owns the concern; add a specialist only when its independent behavior changes the same work.

Routing procedure

Read the task and the Kotlin source that makes the code-design concern concrete.
If one focused skill clearly matches, load it directly and stop routing.
Before loading a Compose skill, point to a concrete Compose API or composable in the inspected source, or to an explicit request to create or design Compose code. A hypothetical UI consumer is not evidence. If neither form of evidence exists, stay in the Kotlin cluster even when the task mentions UI, routes, or navigation.
Otherwise, match each observed code signal to the table below and load the smallest skill set that covers the work.
Combine skills only when separate concerns affect the same change; do not load adjacent skills speculatively.
Finish routing when every material concern has one focused owner and those skills are loaded before advice or edits.

Common routes

Task signal	Start with
Broad Compose screen review, local or hoisted UI state, screen state holders, effect APIs, navigation effects, snackbar, analytics, focus requests, or event Flow collection where Compose APIs, a composable screen, or an explicit greenfield Compose request is evidenced	`compose-state-and-effects`
Recomposition, jank, compiler reports, skippability, unstable parameters, frame-rate State reads, back-writing, or `@ReadOnlyComposable`	`compose-performance`
Modifier parameters, root layout placement, variable visual content, primitive content parameters, optional content, or Boolean shape flags	`compose-component-design`
Compose visibility, value, color, size, transition, content swap, or choosing an animation API	`compose-animations`
Keyboard, TV, desktop, D-pad, `FocusRequester`, `focusProperties`, key events, or initial focus behavior	`compose-focus-navigation`
Compose UI tests, screenshot tests, previews, semantics, fake image loading, keyboard input, focus assertions, or interaction state tests	`compose-ui-testing-patterns`
Coroutine scope ownership, `init { launch }`, non-suspending launch APIs, `runBlocking`, cancellation, `StateFlow`, `SharedFlow`, `Channel`, `stateIn`, or one-shot events	`kotlin-concurrency-and-flow`
Kotlin branching, `when` expressions, guard conditions, sealed type exhaustiveness, smart casts, nullable branching, or complex `if`/`else` chains	`kotlin-control-flow`
Kotlin function placement, member versus top-level or extension functions, factories, single-field domain types, value classes, Kotlin Multiplatform source sets, expect/actual, or platform services	`kotlin-api-design`
Planned Gradle execution, a compact Gradle workflow ledger, repeated Gradle failure fingerprints, or a Gradle-centered build, check, warning-cleanup, or failure workflow, including a diagnosis that should stop before another run	`gradle-run`
One ready GitHub issue or in-chat task needs repository-aware planning before a separate implementation session	`to-plan`
Polling or shepherding PRs/MRs, triaging review comments, fixing CI failures, or keeping reviews moving	`shepherd`

Combining skills

For Compose event handling from a component, use compose-state-and-effects, then add kotlin-concurrency-and-flow when event delivery semantics matter.
For performance work, start with compose-performance.
For animations triggered by state, use compose-animations; add compose-state-and-effects for ownership changes and compose-performance for frame-rate values.
For reusable UI components, use compose-component-design.
For tests around focus behavior, use compose-focus-navigation first, then compose-ui-testing-patterns for test shape.
For Kotlin state, concurrency, or platform-boundary work that also changes branching shape, combine the cluster with kotlin-control-flow.
For plain Kotlin navigation transport plus a sealed route mapping, combine kotlin-concurrency-and-flow with kotlin-control-flow. Do not add compose-state-and-effects unless Compose APIs or state/effect ownership are present or explicitly requested as new code.
Do not infer a Compose concern from a possible UI consumer. Route from the inspected source, not from a consumer the task does not provide.
Kotlin or Compose advice with no planned Gradle execution and no existing Gradle workflow evidence does not load gradle-run.

RED/GREEN agent scenarios

RED loads every Compose skill for a screen with local state and a snackbar. GREEN loads compose-state-and-effects first and adds another skill only for an evidenced concern.
Novel case: a reusable card has a modifier problem and animated height. GREEN uses compose-component-design plus compose-animations, not the state cluster by default.
Counterexample: a request only changes a guard condition in common Kotlin. GREEN loads kotlin-control-flow and does not route through API design.
Novel case: plain Kotlin one-shot route delivery and a sealed data-route renderer are reviewed together. GREEN loads kotlin-concurrency-and-flow and kotlin-control-flow, not the Compose state cluster; mentioning a hypothetical UI collector is not Compose evidence.
Greenfield case: a task explicitly asks to design a new composable that collects a one-shot Flow. GREEN loads compose-state-and-effects and kotlin-concurrency-and-flow even though the composable does not exist yet.
Stop case: a compact Gradle ledger repeats the same primary source failure. GREEN loads gradle-run, stops the rerun loop, and names focused source inspection before any fix or command.