agent-architecht

Architect Android apps with Clean Architecture, Hilt DI, and layer boundaries.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/pliniou/loto-generator --skill agent-architecht
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-architecht
Source: https://github.com/pliniou/loto-generator/tree/main/.windsurf/skills/agent-architecht
Command: npx skills add https://github.com/pliniou/loto-generator --skill agent-architecht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces a scalable Android app architecture using Clean Architecture principles, ensuring clear separation between UI, domain, and data layers and guiding consistent, testable code.

Core Features & Use Cases

  • Establish Clean Architecture with dedicated domain, data, and UI layers and a strict dependency flow.
  • Configure Hilt-based dependency injection across layers, including modular wiring and scoped components.
  • Promote MVVM with repository and use-case patterns to enable testability and maintainability.
  • Guide modularization strategies (modules or packages) and contracts/interfaces to swap data sources without impacting business logic.
  • Provide a living blueprint for onboarding new developers and aligning engineering practices.

Quick Start

Draft an architecture blueprint for the Android app outlining layers, DI, and use-case boundaries, suitable for a kick-off meeting.

Frequently Asked Questions about agent-architecht

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

FAQPage Schema
How do I structure an Android app using Clean Architecture and Hilt?▼

Structure an Android app using Clean Architecture and Hilt by defining strict presentation, domain, and data layers with dependency-inversion rules, wiring scoped Hilt components across modules to ensure testability and maintainable code.

What is the best way to enforce dependency inversion in an MVVM Android app?▼

Enforce dependency inversion in an MVVM Android app by establishing clear layer boundaries and using repository and use-case patterns, ensuring the domain layer defines contracts that data sources implement without impacting business logic.

Can I use this Android architecture blueprint for modularizing a large repository?▼

You can use this Android architecture blueprint for modularizing a large repository by applying its modularization strategies and interface contracts to separate data sources and build extensible, team-scalable implementations.

How do I manage asynchronous flows in a clean Android architecture?▼

Manage asynchronous flows in a clean Android architecture by applying coroutine-based patterns across use cases and repositories, keeping data operations non-blocking and presentation layers consistently fed.

Does this Clean Architecture approach work with existing Hilt dependency injection setups?▼

This Clean Architecture approach works with existing Hilt setups by guiding modular wiring and scoped component configuration across dedicated layers, aligning current dependency injection with strict architectural boundaries.