Guide Android domain layer implementation with stateless, main-safe use cases.
npx skills add https://github.com/tajemniktv/TajsOS --skill domain-layer-tajemniktv
Please help me install this Agent Skill. Skill: domain-layer Source: https://github.com/tajemniktv/TajsOS/tree/main/.agent/skills/domain-layer Command: npx skills add https://github.com/tajemniktv/TajsOS --skill domain-layer-tajemniktv
This Skill eliminates the common issue of bloated, hard-to-test ViewModels in Android apps by providing clear guidance for implementing a proper domain layer that separates business logic from UI and data layers.
Use the domain-layer skill to review your existing Android ViewModel and extract its complex business logic into a compliant, testable use case following Google's official guidelines.
High-intent search queries and answers about installing and using this skill.
To extract business logic from a bloated Android ViewModel, implement a domain layer with stateless use cases. This separates complex logic from UI components, ensuring your ViewModels remain lean, main-safe, and highly testable.
You need a domain layer in your Android Kotlin app when handling complex, multi-step business logic, requiring code reuse across ViewModels, or enforcing strict testability requirements that exceed simple UI or data layer operations.
Android use cases should follow standard naming conventions and implement the operator fun invoke() rule. This allows use case classes to be executed like functions, maintaining statelessness, main-safety, and consistency across your domain layer.
Common anti-patterns when implementing use cases in Kotlin include creating redundant proxy use cases that add no logic, and introducing Android framework dependencies into the domain layer, which breaks testability, main-safety, and architecture compliance.
Yes, the Android domain layer requires proper dependency injection for use cases. Injecting repositories into use cases ensures they remain main-safe, stateless, and fully testable without direct Android framework dependencies.
To validate architecture compliance for Android domain layer PRs, use a review checklist to verify business logic placement, statelessness, and proper dependency injection, ensuring no Android framework dependencies leak into the domain layer.
jhparktimeStructure Android projects into UI, Domain, and Data layers with Hilt.
solrac97grGenerate Go use cases, DTOs, and unit tests with TDD and clean architecture.
NNPopovStructure Flutter apps into layered UI, logic, and data boundaries.
mrsorbateRefactor monolithic architectures into modular bounded contexts with a microkernel plugin system.
