Using chrisbanes skills

Core principle

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

Routing procedure

1. Read the task and the Kotlin source that makes the concern concrete.
2. If one focused skill clearly matches, load it directly and stop routing.
3. 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.
4. Match each observed code signal to the table below.
5. Add a second skill only when it owns an independent decision in the same change; do not load adjacent skills speculatively.
6. Finish routing when every material concern has one focused owner and those skills are loaded before advice or edits.

Common routes

Combination boundaries

• Add kotlin-concurrency-and-flow to Compose state work only when delivery, replay, sharing, or cancellation is a separate concern. Add state ownership or performance only when animation work changes that concern too.
• Pair focus navigation with UI testing when the task also needs a test shape.
• Add kotlin-control-flow when a Kotlin concern also changes branching. Plain Kotlin route delivery plus a sealed mapping stays in the Kotlin cluster; do not add Compose without the evidence required in step 3.
• Load gradle-run only for planned Gradle execution or an existing Gradle workflow, not incidental Kotlin or Compose advice.