← ClaudeAtlas

build-kotlin-androidlisted

Implement Kotlin-first Android app or library changes, including activities, fragments, services, receivers, Compose UI, XML/AppCompat UI, AndroidX, lifecycle-aware coroutines, state, persistence touchpoints, resources, accessibility labels, navigation touchpoints, tests, lint, and validation while preserving repo conventions.
gaelic-ghost/socket · ★ 6 · AI & Automation · score 75
Install: claude install-skill gaelic-ghost/socket
# Build Kotlin Android ## Purpose Implement Kotlin-first Android changes while preserving the repository's architecture, UI system, resources, and validation path. The skill should be deep enough for common Compose and XML UI work without pretending to replace future specialized UI skills. ## Source Check Use repo-local Android files, checked-out dependency sources, and Dash.app docsets opportunistically when they cover exact Gradle, Java, or local command questions. Use official documentation as authority for Android APIs, Compose, AndroidX, lifecycle, resources, accessibility, and version-sensitive behavior: - [Android Developers documentation](https://developer.android.com/docs) - [Jetpack Compose documentation](https://developer.android.com/compose) - [Android app architecture guide](https://developer.android.com/topic/architecture) - [Kotlin documentation](https://kotlinlang.org/docs/home.html) - [AndroidX documentation](https://developer.android.com/jetpack/androidx) Translate documentation into repository-specific code, resource, lifecycle, or validation decisions. ## Implementation Workflow 1. Inspect existing conventions: - package structure and module boundaries - activities, fragments, services, receivers, workers, or navigation owners - Compose versus XML/AppCompat ownership - ViewModel, state holder, repository, dependency injection, persistence, and background-work patterns - resource naming, theming, strings, dimensions, and accessibilit