🤖 Android AI Agent Kit

A structured AI agent system for Android development — Kotlin + Jetpack Compose. Designed to work with Google Gemini / AI coding assistants.

What is this?

A collection of specialized AI agents, skill files, and workflow commands that turn a generic AI assistant into an expert Android developer — following Clean Architecture, MVVM, Jetpack Compose, and Hilt DI best practices.

📁 Structure

.agent/
├── ARCHITECTURE.md          # System overview & quick reference
├── agents/                  # Agent definitions (6 specialists)
│   ├── mobile-developer.md
│   ├── project-planner.md
│   ├── debugger.md
│   ├── security-auditor.md
│   ├── test-engineer.md
│   └── explorer-agent.md
├── workflows/               # Slash commands (7 workflows)
│   ├── brainstorm.md
│   ├── enhance.md
│   ├── plan.md
│   ├── orchestrate.md
│   ├── debug.md
│   ├── test.md
│   └── status.md
└── skills/                  # Knowledge base (15 skill sets)
    ├── android-architecture/
    ├── android-compose-patterns/
    ├── android-navigation/
    ├── android-local-data/
    ├── android-networking/
    ├── android-performance/
    ├── android-testing/
    ├── mobile-design/
    ├── brainstorming/
    ├── plan-writing/
    ├── systematic-debugging/
    ├── code-review-checklist/
    ├── clean-code/
    ├── tdd-workflow/
    └── testing-patterns/

🤖 Agents

| Agent | Role | |-------|------| | mobile-developer | Android implementation — Compose, MVVM, Clean Arch, Hilt | | project-planner | Break down tasks into verifiable, dependency-ordered plans | | debugger | Systematic root cause analysis — 4-phase debugging process | | security-auditor | OWASP, auth, token, encryption review | | test-engineer | Unit tests, TDD, coverage — JUnit 5 + MockK + Turbine | | explorer-agent | Codebase discovery, architecture mapping, feasibility analysis |

🔄 Workflow Commands

| Command | When to Use | |---------|-------------| | /brainstorm | Multiple valid approaches — explore trade-offs before coding | | /plan | Complex feature (5+ files) — produce a structured plan file | | /enhance | Add or update a feature with conflict check + impact analysis | | /orchestrate | Multi-agent coordination for end-to-end feature delivery | | /debug | Bug, crash, or unexpected behavior — systematic investigation | | /test | Generate and run tests after implementation | | /status | Current progress snapshot — plans, agents, health, blockers |

🔀 Typical Workflow

Unclear approach?  →  /brainstorm  →  pick option
Complex task?      →  /plan        →  approve plan
Implement:         →  /enhance  or  /orchestrate
After code:        →  /test        →  /status
Bug appears?       →  /debug       →  fix

🛠️ Tech Stack it Knows

• Language: Kotlin
• UI: Jetpack Compose + Material 3
• Architecture: MVVM / MVI + Clean Architecture
• DI: Hilt
• Async: Coroutines + Flow / StateFlow
• Navigation: Compose Navigation (type-safe routes)
• Network: Retrofit + OkHttp
• Local Data: Room + DataStore
• Testing: JUnit 5 + MockK + Turbine + Compose UI Test
• Image: Coil

📄 License

MIT — free to use and adapt for your own projects.