android-kotlin
by alinaqiandroid-kotlin skill guide for Android Kotlin development with Coroutines, Flow, Jetpack Compose, Hilt, and MockK. Use it to work on app layers, Gradle Kotlin DSL, and repo-aware UI, domain, and data changes with less guesswork.
This skill scores 66/100, which means it is listable but best presented with caveats: it offers real Android Kotlin workflow guidance, yet users should expect limited operational packaging and little automation support. For directory users, it is a credible install candidate if they want a path-aware Android/Kotlin coding guide rather than a tool-driven workflow skill.
- Clear trigger metadata: it specifies when-to-use, user-invocable status, and file path patterns for Kotlin/Gradle/Android files.
- Substantive workflow content: the body is large, with project structure guidance and multiple workflow-related sections rather than placeholder text.
- Relevant domain coverage: it explicitly targets Android Kotlin work with Coroutines, Jetpack Compose, Hilt, and MockK testing.
- No install command and no supporting scripts/resources, so adoption depends on the user already understanding how to apply the skill manually.
- No repo/file references or explicit constraints-heavy playbook, which limits confidence for edge cases and complex handoff execution.
Overview of android-kotlin skill
What android-kotlin is for
The android-kotlin skill helps you work on Android app code written in Kotlin, especially when the project uses Coroutines, Flow, Jetpack Compose, Hilt, and MockK. It is most useful when you need an AI assistant to understand an Android codebase’s structure and produce changes that fit the app’s layers instead of giving generic Kotlin advice.
Best-fit use cases
Use the android-kotlin skill when you are updating *.kt or *.kts files, wiring dependency injection, editing Compose screens, or adjusting repository, domain, and UI code together. It is a good fit for the android-kotlin for Frontend Development workflow when the frontend is the Android UI layer, not a web stack.
What it helps you avoid
This skill is valuable when you want less guesswork around Android project layout, Gradle Kotlin DSL, and common app architecture boundaries. It is less useful if your task is unrelated to Android source, or if you only need a one-off snippet without respecting the project’s structure.
How to Use android-kotlin skill
Install it in the right context
Use the android-kotlin install flow when your workspace includes Android Kotlin sources and you want the assistant to operate with repo-aware context. A typical install command is:
npx skills add alinaqi/claude-bootstrap --skill android-kotlin
Read the right files first
Start with SKILL.md, then inspect app/build.gradle.kts, the root build.gradle.kts, and any *.kt files that match your target feature. Because this repo has no extra rules/, references/, or resources/ files, the skill body itself is the main source of guidance.
Give a task-shaped prompt
The best android-kotlin usage is specific about feature, layer, and constraints. For example, instead of “fix this screen,” ask for “update the Compose screen and ViewModel for login state, preserve Hilt injection, keep Flow-based state, and avoid changing the repository interface.”
Use a layer-aware workflow
A strong android-kotlin guide is to first identify whether the change belongs in data, domain, or UI, then ask the assistant to modify only those layers. If the request spans multiple layers, say so explicitly and name the files or packages involved so the output stays aligned with the project structure.
android-kotlin skill FAQ
Is android-kotlin only for Android app code?
Yes, it is centered on Android Kotlin development. It is not meant for generic backend Kotlin, plain JVM utilities, or non-Android frontend work.
Do I need Jetpack Compose or Hilt to use it?
No, but those are the main patterns surfaced in the skill. If your app uses older XML views or a different DI setup, the fit may be weaker and you should state that up front.
How is this different from a normal prompt?
A normal prompt can generate Kotlin code, but the android-kotlin skill is aimed at keeping changes consistent with Android project structure, Gradle Kotlin DSL, Coroutines, Flow, Compose, Hilt, and MockK testing. That matters when you want code that matches an existing app instead of a generic example.
Is it good for beginners?
Yes, if you want guidance inside an existing Android codebase. It is less beginner-friendly if you do not know which layer your change belongs in or if you cannot describe the expected UI, state, or data flow.
How to Improve android-kotlin skill
Specify the app layer and desired outcome
The biggest quality boost comes from naming the layer: UI, domain, data, DI, or build configuration. Also include the expected outcome, such as “add retry behavior,” “expose state from ViewModel,” or “wire a new repository through Hilt.”
Provide constraints that shape the implementation
Mention what must not change, such as public APIs, navigation routes, test style, or existing coroutine scopes. If your project has conventions for naming, package placement, or error handling, include them so the android-kotlin skill does not invent a new pattern.
Iterate from structural feedback
If the first output is too broad, ask for a narrower pass: “limit changes to ui/feature and FeatureViewModel,” or “show only the Gradle Kotlin DSL diff.” This usually improves the result more than asking for a fully polished answer on the first try.