Agent Skills
› midudev/autoskills
› android-kotlin-core
android-kotlin-core
GitHub指导在Android应用中使用Kotlin惯用法，涵盖空安全、数据类、密封类型、扩展函数及集合管道。用于清理Java风格代码、优化UI状态模型并确保代码的安全性与可维护性。
Trigger Scenarios
Android Kotlin代码清理与重构
将冗长的Java风格Kotlin代码转换为惯用写法
使用密封类管理UI状态
Install
npx skills add midudev/autoskills --skill android-kotlin-core -g -y
SKILL.md
Frontmatter
{
"name": "android-kotlin-core",
"metadata": {
"tags": [
"android",
"kotlin",
"foundation",
"api-design"
],
"owners": [
"@android-agent-skills\/maintainers"
],
"version": "0.1.0",
"category": "foundations",
"triggers": {
"exclude": [
"full gradle upgrade",
"compose navigation only",
"release play console setup"
],
"include": [
"kotlin cleanup in android app",
"convert verbose android java-style kotlin",
"sealed classes for ui state",
"extension functions for android feature",
"improve kotlin readability in android module"
]
},
"test_targets": [
"examples\/orbittasks-compose",
"examples\/orbittasks-xml",
"benchmarks\/triggers.jsonl"
]
},
"description": "Use Kotlin idioms safely in Android apps, including nullability, data classes, sealed types, extension functions, and collection pipelines."
}
Android Kotlin Core
When To Use
- Use this skill when the request is about: kotlin cleanup in android app, convert verbose android java-style kotlin, sealed classes for ui state.
- Primary outcome: Use Kotlin idioms safely in Android apps, including nullability, data classes, sealed types, extension functions, and collection pipelines.
- Handoff skills when the scope expands:
android-state-managementandroid-testing-unit
Workflow
- Map the request to the current Android stack, module boundaries, and minimum supported API level.
- Inspect the existing implementation for implicit assumptions, duplicate helpers, and outdated patterns.
- Apply the smallest change that improves correctness, readability, and long-term maintainability.
- Validate the result against the relevant showcase app path and repo benchmarks.
- Hand off adjacent work to the next specialized skill only after the core foundation is stable.
Guardrails
- Prefer official Android and Kotlin guidance over custom local conventions when they conflict.
- Keep public APIs boring and explicit; avoid clever abstractions that hide Android lifecycle costs.
- Do not mix architectural cleanup with product behavior changes unless the request explicitly needs both.
- Document any compatibility constraints that will affect old modules or generated code.
Anti-Patterns
- Sprinkling helpers across modules without a clear ownership boundary.
- Introducing framework-specific code into pure domain or data layers.
- Refactoring every adjacent file when only one contract needed to change.
- Leaving migration notes implied instead of writing them down.
Examples
Happy path
- Scenario: Tighten domain and UI state models with sealed interfaces and immutable data.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest
Edge case
- Scenario: Guard nullable platform values crossing the XML activity boundary.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest
Failure recovery
- Scenario: Refactor broad helper objects into focused extensions without breaking call sites.
- Command:
python3 scripts/eval_triggers.py --skill android-kotlin-core
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
Version History
- 0ec7253 Current 2026-07-24 20:51
