using-chrisbanes-skills
Router skill for selecting appropriate Jetpack Compose and Android development tools.
Install
mkdir -p .claude/skills/using-chrisbanes-skills && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11450" && unzip -o skill.zip -d .claude/skills/using-chrisbanes-skills && rm skill.zipInstalls to .claude/skills/using-chrisbanes-skills
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when a Kotlin, Android, or Jetpack Compose task is too broad for any single focused skill to obviously apply, especially for general review, refactor, architecture, state, performance, testing, or UI API design work.Key capabilities
- →Choose focused skills for a task
- →Load relevant focused skills
- →Provide detailed advice for Kotlin, Android, or Jetpack Compose tasks
- →Edit code for Kotlin, Android, or Jetpack Compose tasks
How it works
This skill acts as a router, selecting specific sub-skills based on the development task and then loading those skills to provide detailed advice or code edits.
Inputs & outputs
When to use using-chrisbanes-skills
- →Review compose screen
- →Refactor android architecture
- →Debug state management
About this skill
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.
- 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, snackbar, analytics, focus requests, or event Flow collection | 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 |
| One ready GitHub issue or confirmed conversation specification 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 addkotlin-concurrency-and-flowwhen event delivery semantics matter. - For performance work, start with
compose-performance. - For animations triggered by state, use
compose-animations; addcompose-state-and-effectsfor ownership changes andcompose-performancefor frame-rate values. - For reusable UI components, use
compose-component-design. - For tests around focus behavior, use
compose-focus-navigationfirst, thencompose-ui-testing-patternsfor test shape. - For Kotlin state, concurrency, or platform-boundary work that also changes branching shape, combine the cluster with
kotlin-control-flow.
RED/GREEN agent scenarios
- RED loads every Compose skill for a screen with local state and a snackbar.
GREEN loads
compose-state-and-effectsfirst 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-designpluscompose-animations, not the state cluster by default. - Counterexample: a request only changes a guard condition in common Kotlin.
GREEN loads
kotlin-control-flowand does not route through API design.
When not to use it
- →A request already clearly matches a focused skill
How it compares
This skill directs to specialized sub-skills for specific development areas, unlike a generic approach that might offer general advice.
Compared to similar skills
using-chrisbanes-skills side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| using-chrisbanes-skills (this skill) | 0 | 1mo | No flags | Beginner |
| android-kotlin | 7 | 4mo | No flags | Intermediate |
| reviewing-changes | 1 | 3mo | No flags | Intermediate |
| kmp-cmp-app-builder | 0 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by chrisbanes
View all by chrisbanes →You might also like
android-kotlin
alinaqi
Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing
reviewing-changes
bitwarden
Guides Android code reviews with type-specific checklists and MVVM/Compose pattern validation. Use when reviewing Android PRs, pull requests, diffs, or local changes involving Kotlin, ViewModel, Composable, Repository, or Gradle files. Triggered by "review PR", "review changes", "check this code", "Android review", or code review requests mentioning bitwarden/android. Loads specialized checklists for feature additions, bug fixes, UI refinements, refactoring, dependency updates, and infrastructure changes.
kmp-cmp-app-builder
firdaus1453
>
Android Navigation
li-lance
Standards for Jetpack Navigation Compose (Type-safe)
compose-skill
tajemniktv
>
mobile-agent
Wolfof420Street
Mobile specialist for Compose Multiplatform, Kotlin Multiplatform, and cross-platform mobile development