Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub joshuarweaver/cascade-code-languages-misc-2 --plugin pluginagentmarketplace-custom-plugin-androidHow this command is triggered — by the user, by Claude, or both
Slash command
/android-development-assistant:dev-guideThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /dev-guide - Android Development Guide Complete professional Android development guide covering best practices, patterns, and production workflows. ## Learning Path ### Beginner (100-150 hours) 1. **Kotlin Fundamentals** (30-40 hours) - Variables, functions, classes - Extension functions - Basic coroutines 2. **Android Core** (40-50 hours) - Activities and lifecycle - Fragments - Intents and navigation - Data persistence 3. **First App Project** (30-60 hours) - Simple todo app with database - Multiple screens - CRUD operations ### Intermediate (100-150 ...
/mobileSets up iOS/Android mobile apps with architecture patterns, platform configs (Xcode/Gradle/Flutter), signing/provisioning, store submission prep, and performance audits. Supports flags like --ios, --perf.
/guidelines-generateGenerates a comprehensive development guideline document for a specified language like Go or Python, customizable via optional parameters for ORM, web framework, DB, testing, logging, and more.
/f5-mobileGenerates mobile app screens, widgets, models, services, and more for auto-detected stack (Flutter, React Native Expo, Android Kotlin, iOS Swift). Outputs files list, architecture diagram, next steps.
Share bugs, ideas, or general feedback.
Complete professional Android development guide covering best practices, patterns, and production workflows.
Kotlin Fundamentals (30-40 hours)
Android Core (40-50 hours)
First App Project (30-60 hours)
Jetpack Modern (40-50 hours)
Architecture Patterns (40-50 hours)
Real-World App (20-50 hours)
Production Quality (50-100 hours)
Capstone Project (50-100+ hours)
UI Layer:
- Activities/Fragments (or Jetpack Compose)
- Navigation Component
- Material Design 3
Architecture:
- MVVM with ViewModel
- Repository pattern
- Hilt for DI
Data:
- Room database
- Retrofit for APIs
- DataStore for preferences
Testing:
- JUnit 4/5
- Mockk for mocking
- Espresso for UI tests
DevOps:
- GitHub Actions
- Gradle build automation
- Play Store deployment
myapp/
├── app/
│ ├── src/main/
│ │ ├── java/
│ │ │ └── com/example/app/
│ │ │ ├── data/
│ │ │ │ ├── local/
│ │ │ │ ├── remote/
│ │ │ │ └── repository/
│ │ │ ├── domain/
│ │ │ │ ├── model/
│ │ │ │ └── repository/
│ │ │ ├── presentation/
│ │ │ │ ├── ui/
│ │ │ │ └── viewmodel/
│ │ │ └── di/
│ │ └── res/
│ ├── src/test/
│ └── src/androidTest/
├── build.gradle.kts
└── settings.gradle.kts
✅ Follow SOLID principles ✅ DRY (Don't Repeat Yourself) ✅ KISS (Keep It Simple, Stupid) ✅ Clean code practices ✅ Consistent naming conventions
✅ Separation of concerns ✅ Dependency injection ✅ Repository pattern ✅ Testable design ✅ Single source of truth
✅ Unit tests for business logic (70%) ✅ Integration tests (20%) ✅ UI tests (10%) ✅ Mock external dependencies ✅ Aim for 80%+ coverage
✅ No memory leaks ✅ Efficient database queries ✅ Proper coroutine scoping ✅ 60+ FPS rendering ✅ Fast app startup
✅ No hardcoded secrets ✅ HTTPS for all APIs ✅ Encrypted sensitive data ✅ Proper permission handling ✅ Input validation
❌ Not understanding lifecycle ❌ Holding context in singletons ❌ Heavy operations on main thread ❌ Memory leaks from listeners ❌ Tight coupling between layers ❌ Skipping tests ❌ Not handling configuration changes ❌ Storing secrets in code
✅ App runs without crashes ✅ 80%+ test coverage ✅ No memory leaks ✅ Performs at 60 FPS ✅ Follows SOLID principles ✅ Clear code structure ✅ Documented code ✅ Proper error handling ✅ Security reviewed ✅ Published on Play Store
/code-examplesReady to build professional Android apps? Start with the learning path above!