android-engineering-core
This skill is used to implement Android features within the existing Kotlin, Compose, Room, Hilt and Navigation architecture, including data, navigation and background work.
Best use case
android-engineering-core is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill is used to implement Android features within the existing Kotlin, Compose, Room, Hilt and Navigation architecture, including data, navigation and background work.
Teams using android-engineering-core should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-engineering-core/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-engineering-core Compares
| Feature / Agent | android-engineering-core | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill is used to implement Android features within the existing Kotlin, Compose, Room, Hilt and Navigation architecture, including data, navigation and background work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android Engineering and Core Implementation Skill ## Purpose Implement the shaped and designed Android feature in the existing architecture, covering data persistence, business logic, navigation, reminders and background behaviour. ## When to Use Use this skill once product shaping and UX design are complete and the UI structure is known. ## Outputs - Updated Room entities, DAOs and migrations when required - Repository and use-case logic - ViewModel state and event handling - Navigation wiring - Integration with AlarmManager, notifications or other platform components ## Procedure 1. Confirm the slice fits within the current stack: - Kotlin, Coroutines and Flow - Room for local data - Hilt for dependency injection - Jetpack Navigation and Compose for UI 2. Apply the smallest data changes needed: - Adjust existing entities where possible. - Add new entities only when the UX slice truly demands it. - Create safe Room migrations for any schema changes. 3. Map user actions from the UX design to ViewModel events: - Define clear intent functions (for example onAddTask, onToggleComplete). - Keep side effects (saving, scheduling reminders) in the ViewModel or use-case layer, not in composables. 4. Implement repositories or use-cases: - Keep them focused on data and business logic. - Expose Flows or suspend functions as appropriate. 5. Wire navigation: - Add or adjust routes in the NavHost. - Pass arguments via navigation arguments and SavedStateHandle. 6. Integrate platform services carefully: - Use AlarmManager, Notifications and BroadcastReceivers for reminders when required. - Handle boot rescheduling if reminders depend on time. - Avoid new background frameworks unless necessary. ## Guardrails - Do not change the overall architecture or introduce new frameworks. - Do not move logic into composables. - Do not add network sync, backends or multi-device features unless explicitly required by shaping. - Prefer small, incremental changes over broad refactors.
Related Skills
android
Build, review, and refactor Android mobile apps (Kotlin) using modern Android patterns. Use for tasks like setting up Gradle modules, Jetpack Compose UI, navigation, ViewModel/state management, networking (Retrofit/OkHttp), persistence (Room/DataStore), DI (Hilt/Koin), testing, performance, release builds, and Play Store readiness.
android-watch-logs
Start real-time log streaming from connected Android device using adb logcat. Shows only app's log messages. Use when monitoring app behavior, debugging, or viewing Android logs.
android-use
Control Android devices via ADB commands - tap, swipe, type, navigate apps
android-supabase
Supabase integration patterns for Android - authentication, database, realtime subscriptions. Use when setting up Supabase SDK, implementing OAuth, querying database, or setting up realtime.
android-stop-app
Stop the Android app running on connected device. Cleanly terminates the app using force-stop. Use when stopping the app for debugging, testing, or cleanup.
android-project
Navigate and analyze Android project structure, modules, and dependencies. Use when exploring project structure, finding related files, analyzing dependencies, or locating code patterns.
android-notification-builder
Эксперт Android notifications. Используй для push notifications, channels и notification patterns.
android-motion-specialist
Expert Android developer for the Motion Detector project. Use this skill when working on Camera2 API integration, motion detection algorithms, Android networking (LAN sockets + Supabase Realtime), debugging crashes, or any Android/Kotlin development tasks specific to this sprint timing application.
android-kotlin
Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing
android-kotlin-development
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
android-keystore-generation
Generate production and local development keystores for Android release signing
android-gradle
Automate Gradle tasks for Android projects - build, test, coverage, clean. Use when building APKs, running unit tests, generating coverage reports, or checking dependencies.