android-architectureApp architecture & module conventions — layering, :feature modularization, state management (detect then follow), coroutine/Flow concurrency, DI, version catalog. Invoke before structuring features, ViewModels/stores, modules, or DI wiring.
android-build-releaseAndroid build and release engineering — Gradle convention plugins, the version catalog, flavors and build types, signing configuration, ProGuard/R8, gradle.properties performance flags, and store/app distribution. Invoke before changing build configuration, signing, minification, or release distribu
android-ciAndroid CI pipelines — GitHub Actions job structure (lint → test → assemble → bundle → distribute), Gradle caching, submodule checkout, release signing from secrets, and the CI/DevOps boundary. Invoke before writing or changing CI workflow YAML for an Android project.
android-compose-uiCompose UI conventions — stateful/stateless split, state hoisting, lifecycle-aware state collection, side-effect discipline, previews, recomposition hygiene. Invoke before building or refactoring Compose screens and components.
android-dataData layer conventions — repository interface/impl co-location, DTO↔domain mapping, persistence choice, suspend/Flow networking, dispatcher discipline, secure storage. Invoke before building repositories, data sources, persistence, or network/realtime integrations.
android-debuggingAndroid root-cause analysis — coroutine/Flow, Compose recomposition, memory-leak and null/`!!` bug categories with their likely causes; Logcat and heap-dump commands; Layout Inspector and Profiler workflow. Invoke before diagnosing a crash, ANR, leak, or unexpected behaviour in an Android project.
android-docs-vaultAndroid documentation duties — the Obsidian vault canon (structure, typed edges, generated artifacts), hook-created stubs, the testTag index, the stack table, KDoc standards, and the Definition of Done that gates the PR. Invoke before writing docs, filling vault stubs, or opening a PR on an Android
android-e2eAndroid E2E and UI automation — Compose UI Test (createAndroidComposeRule, testTag selectors, list matchers), Maestro YAML flows, accessibility/TalkBack audits, adb and instrumented Gradle tasks. Invoke before writing or running end-to-end, instrumented, or accessibility tests on an Android project.
android-navigationNavigation conventions — type-safe @Serializable routes over strings, per-module route ownership, typed arguments, ViewModel-sourced nav events, deep-link validation. Invoke before adding routes, graphs, screen transitions, or deep links.
android-requirementsAndroid requirements engineering — discovery, module-placement (DDD bounded contexts across :feature:<name>), risk assessment, phased roadmap, and the Android feature-analysis deliverable. Invoke before writing requirements, user stories, acceptance criteria, or an implementation plan for an Android
android-reviewAndroid code-review dimensions — Kotlin correctness, layering, Compose patterns and testTags, navigation, design system, DI, persistence/logging, performance, and vault freshness. Invoke before reviewing a diff in an Android (Kotlin) project.
android-security-masvsAndroid security audit against OWASP MASVS/MASTG — secrets, TLS and pinning, secure storage and Keystore, auth and biometrics, realtime/billing boundaries, manifest and exported components, ProGuard/R8, plus the MASVS control map and the OWASP Mobile Top 10 cross-map. Invoke before auditing an Andro
android-testingAndroid unit and integration testing — MockK, Turbine, kotlinx-coroutines-test, Robolectric, Kover; ViewModel/store, repository and mapper patterns; what to test and what not to; Gradle test tasks. Invoke before writing or fixing JVM unit tests in an Android (Kotlin) project.
datastore-conventionsProto-DataStore-specific persistence idioms — one DataStore<T> per file, a typed Serializer<T> with default + corruption handler, Flow reads, atomic updateData writes, SharedPreferences/Data migrations, and keeping secrets out of the plaintext store. Invoke before adding or changing a DataStore inst
hilt-conventionsDagger/Hilt-specific DI idioms — constructor injection, @HiltAndroidApp/@AndroidEntryPoint entry points, @HiltViewModel, @Module + @InstallIn with @Binds over @Provides, deliberate scoping, dispatcher qualifiers, and KSP compiler. Invoke before adding or changing Hilt modules, components, scopes, or
koin-conventionsKoin-specific DI idioms — module DSL (single/factory/viewModel), constructor injection via get(), startKoin/androidContext bootstrap, koinViewModel in Compose, deliberate scoping, and avoiding the service-locator anti-pattern. Invoke before adding or changing Koin modules, definitions, scopes, or st
ktor-conventionsKtor-client-specific networking idioms — a single long-lived HttpClient, engine choice, ContentNegotiation with kotlinx-serialization, DEBUG-gated Logging, HttpTimeout, expectSuccess/response validation, and mapping Ktor exceptions to domain Results at the repository boundary. Invoke before adding o
manage-vaultUse to scaffold, repair, or (re)populate the optional Obsidian knowledge vault (`.obsidian-vault/`) for an Android/Kotlin project. One phased, idempotent skill that merges the old setup/fill-vault/update flows: it ensures the vault skeleton + Node scripts exist (adding only what is MISSING, never to
retrofit-conventionsRetrofit/OkHttp-specific networking idioms — suspend/Flow service signatures, single OkHttpClient with ordered interceptors, converter setup, and transport-error mapping to domain Results. Invoke before adding or changing Retrofit service interfaces, OkHttp client config, or API DTO mapping. Layer p
room-conventionsRoom-specific persistence idioms — @Entity/@Dao/@Database structure, suspend/Flow DAO signatures, @Transaction atomicity, parameterized queries, migrations with exportSchema, KSP compiler, and entity↔domain mapping at the boundary. Invoke before adding or changing Room entities, DAOs, the database c
workmanager-conventionsWorkManager-specific idioms — CoroutineWorker over threaded Worker, unique enqueue with an explicit ExistingWorkPolicy, meaningful Constraints + backoff, WorkerFactory-based DI, idempotent doWork with correct Result, small non-sensitive inputData, WorkInfo Flow observation, and work-testing. Invoke