Yes. A Composable should not call a repository directly. That couples presentation to data access, makes recomposition and lifecycle behavior harder to control, and makes the UI harder to test. Use unidirectional data flow instead: ```text Composable --events--> ViewModel --calls--> UseCase --> Repository Composable <--UiState-- ViewModel ``` The ViewModel should invoke the use case in response to UI events and expose a `StateFlow<UiState>`. The Composable should collect it with `collectAsSta...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill android-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Android Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-android-architecture-c9c936ca)More formats (shields.io, HTML) on the badges page.
Yes. A Composable should not call a repository directly. That couples presentation to data access, makes recomposition and lifecycle behavior harder to control, and makes the UI harder to test.
Use unidirectional data flow instead:
```text
Composable --events--> ViewModel --calls--> UseCase --> Repository
Composable <--UiState-- ViewModel
```
The ViewModel should invoke the use case in response to UI events and expose a `StateFlow<UiState>`. The Composable should collect it with `collectAsStateWithLifecycle()` and render the result. Keep repository implementations and data-source details in the data layer, and keep the domain layer free of Android dependencies.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
