tech-android

Apply Android-specific development patterns and Kotlin best practices to Android projects.

16|15|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ravnhq/ai-toolkit --skill tech-android
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-android
Source: https://github.com/ravnhq/ai-toolkit/tree/main/skills/tech-android
Command: npx skills add https://github.com/ravnhq/ai-toolkit --skill tech-android

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android developers need consistent patterns for Kotlin apps to ensure maintainability, reuse, and faster delivery across teams.

Core Features & Use Cases

  • Android architecture guidance (MVVM, Clean Architecture) tailored to Kotlin-based Android projects.
  • Kotlin best practices and Android component integration (Activities, Fragments, ViewModels, LiveData) for robust apps.
  • Use Case: Standardize Android app scaffolding for new Kotlin projects to reduce onboarding time and improve code quality.

Quick Start

  • Apply Android-specific rules to a Kotlin Android project and align with platform-mobile guidelines.

Frequently Asked Questions about tech-android

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce MVVM architecture in a Kotlin Android project?

To enforce MVVM architecture in a Kotlin Android project, apply Android-specific rules for component integration using ViewModels and LiveData to ensure maintainability and consistent app scaffolding.

What is the best way to standardize Android app scaffolding for new Kotlin projects?

Standardizing Android app scaffolding for new Kotlin projects involves applying architecture guidance and Kotlin best practices to reduce onboarding time and improve code quality across teams.

Can I use this for Android component integration with Activities and Fragments?

Yes, you can use this for Android component integration with Activities, Fragments, and ViewModels, as it extends the platform-mobile baseline with Android-specific lifecycle management rules.

Do I need Clean Architecture guidelines to manage Android lifecycles in Kotlin?

You do not strictly need Clean Architecture guidelines to manage Android lifecycles in Kotlin, but applying tailored architecture patterns helps enforce best practices for robust component integration.