What problem does it solve?
Android developers building apps for diverse form factors often struggle with inconsistent architecture that leads to unmaintainable code, difficult testing, and poor cross-device support when scaling projects.
Core Features & Use Cases
- Standardized Three-Layer Structure: Clear guidance on the UI, Domain, and Data layers with strict dependency rules to prevent tight coupling between components.
- Core Design Principles: Built-in rules for separation of concerns, single source of truth, unidirectional data flow, and main-safety to reduce bugs and improve testability.
- Practical Implementation Guidance: Best practices for dependency injection with Hilt, multi-module project structure, and a ready-to-use PR checklist to enforce architecture standards.
- Use Case: A developer building a new TajsOS Android feature can use this skill to structure their code correctly from the start, avoiding common pitfalls like storing state in Activities or creating circular module dependencies.
Quick Start
Use the app-architecture skill to review your Android project's module structure and identify violations of the dependency rule or missing single source of truth implementations.
