Android Concurrency Standards
SkillCommunicationWrite correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Android Concurrency Standards skill
What this skill tells your AI
The instructions your AI receives, as published by hoangnguyen0403/agent-skills-standard in skills/android/android-concurrency/SKILL.md and read by ahel’s review.
Priority: P0 (CRITICAL)
Implementation Guidelines
Structured Concurrency
- Scopes: Always use
viewModelScope(VM) orlifecycleScope(Activity/Fragment). - Dispatchers: INJECT Dispatchers (
DispatcherProvider) for testability. not hardcodeDispatchers.IO.
Flow usage
- Cold Streams: Use
Flowfor data streams. - Hot Streams: Use
StateFlow(State) orSharedFlow(Events). - Replay: Use
SharedFlowwithreplayonly when late subscribers must receive recent events. - Collection: Use
collectAsStateWithLifecycle()(Compose) orrepeatOnLifecycle(Views).
Anti-Patterns
- No GlobalScope: Use viewModelScope or lifecycleScope — never GlobalScope.
- No async/await by default: Prefer simple suspend functions; async only for parallel calls.
References
Canonical response anchors
- Additional task-grounded exact anchors: hardcode
Signals
- GitHub stars
- 565
- Forks
- 163
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
android-concurrency- Source
- github.com/hoangnguyen0403/agent-skills-standard