android-architecture

Selects MVI, MVVM, or Simple Compose for Android projects and generates documentation.

3|Updated Sep 29, 2025
One-click install
npx skills add https://github.com/xtone/ai_development_tools --skill android-architecture-xtone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-architecture
Source: https://github.com/xtone/ai_development_tools/tree/main/android_development/.claude/skills/android-architecture
Command: npx skills add https://github.com/xtone/ai_development_tools --skill android-architecture-xtone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android projects often suffer from unclear architecture decisions, wasted time choosing patterns, and inconsistent package structures. This Skill helps you decide the right architecture (MVI, MVVM, or Simple Compose) based on project traits and generate a coherent structure and documentation.

Core Features & Use Cases

  • Recommend the optimal architecture pattern (MVI, MVVM, or Simple Compose) based on project size, complexity, and team experience.
  • Analyze existing Android projects to assess structure, patterns, and documentation gaps.
  • Generate scaffold artifacts and setup guides to kick off a new project or refactor effort, including example package layouts and guidance docs.

Quick Start

Run /android-architecture analyze on an existing project to generate architecture analysis, or /android-architecture setup to scaffold a chosen pattern. Then use /android-architecture document to generate architecture documentation.

Frequently Asked Questions about android-architecture

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

FAQPage Schema
How do I choose the best Android architecture pattern for my project?

Choosing the best Android architecture pattern involves evaluating project size, complexity, and team experience to select MVI, MVVM, or Simple Compose, ensuring a coherent package structure and clear separation of concerns.

What's the difference between MVI and MVVM when building Android apps with Compose?

MVI enforces unidirectional data flow and state immutability, while MVVM separates state into observable data streams; selecting between them for Compose depends on team familiarity and specific state management complexity.

How do I analyze an existing Android project to find architecture gaps?

Analyzing an existing Android project assesses its current structure, patterns, and documentation gaps to identify inconsistencies, driving recommendations for refactoring towards a more optimal architectural layout.

Can I generate setup guides and scaffolding for a new Android architecture?

Generating setup guides and scaffolding for a new Android architecture creates example package layouts and guidance docs, kicking off projects with a coherent structure based on the chosen MVI, MVVM, or Simple Compose pattern.

When should I use Simple Compose architecture instead of MVVM or MVI?

Simple Compose architecture suits smaller projects or less complex screens where the overhead of MVI or MVVM state management is unnecessary, providing a coherent structure without rigid pattern enforcement.