using-chrisbanes-skills

What problem does it solve? When debugging, benchmarking, or reviewing Kotlin and Jetpack Compose code, it is hard to know which design concern applies before the root cause is known. This Skill acts as a router that inspects the code and task, then loads only the smallest set of focused skills needed before giving advice or editing code. ## Core Features & Use Cases - Signal-based routing: Maps concrete code signals (e.g., LaunchedEffect, StateFlow, recomposition, remember { mutableStateOf(...) }) to the right focused skill via a routing table. - Minimal skill loading: Loads one focused skill when it clearly matches, or combines skills only when separate concerns affect the same change. - Broad coverage: Routes across Compose state, side effects, performance, stability, animations, focus, testing, and Kotlin coroutines, Flow, control flow, and multiplatform concerns. - Use Case: During a broad Compose screen review, the router starts with state-hoisting guidance, then adds effects, layout, testing, or performance skills only as the code signals demand. ## Quick Start Ask the assistant to review a Kotlin or Compose file for design issues and let it route to the appropriate focused skills before suggesting changes.