java-android-workflowlisted

Maintain Java-only Android projects and Kotlin/Java interoperability inside Android apps or libraries, including Java source sets, AndroidX Java APIs, annotations, nullability, SAM boundaries, generated bytecode expectations, public API compatibility, tests, lint, and migration guardrails.
gaelic-ghost/socket · ★ 6 · AI & Automation · score 75

Install: claude install-skill gaelic-ghost/socket

# Java Android Workflow ## Purpose Preserve Java Android codebases and make Kotlin/Java boundaries explicit when Android modules are mixed-language. The practical decision is whether to stay Java-only, add Kotlin interop carefully, or route implementation to Kotlin-first guidance without forcing a migration. ## Source Check Use repo-local Java, Kotlin, Gradle, and Android files first. Use Dash.app Java or Gradle docsets opportunistically for installed local reference. Use official documentation as authority for Android-specific APIs, Kotlin Java interop, AndroidX behavior, and version-sensitive rules: - [Android Developers documentation](https://developer.android.com/docs) - [Java documentation](https://docs.oracle.com/en/java/) - [Kotlin Java interoperability documentation](https://kotlinlang.org/docs/java-interop.html) - [AndroidX documentation](https://developer.android.com/jetpack/androidx) - [Android build documentation](https://developer.android.com/build) Translate documentation into concrete API, annotation, source-set, or validation choices. ## Inspection Workflow 1. Inspect source ownership: - `src/main/java` - `src/main/kotlin` - generated sources - public Android library APIs - Java callers of Kotlin code and Kotlin callers of Java code 2. Identify interop boundaries: - nullability annotations - `@JvmName`, `@JvmOverloads`, `@JvmStatic`, `@JvmField`, or `@Throws` - SAM conversions and functional interfaces - checked exceptions a