android-data

Files (1)

• SKILL.md

SKILL.md (first lines)

# Data layer and repositories

## Purpose

Expose app data through repositories; isolate data sources.

## When to load

Data paths and repository files; repository change-impact tasks.

## Inputs

- Domain/repository contracts.
- Remote and local source APIs.

## Outputs

- Repository implementations, mappers, offline-first behavior per FR.

## Rules

- [Data layer](https://developer.android.com/topic/architecture/data-layer)

- One repository per data type; repositories are the only entry to data sources.
- Map DTO/entity → domain where shapes differ.
- UI and ViewModels never depend on data sources directly.
- Flow for observed data; suspend for one-shot operations.
- **Paging 3:** `Pager` + `PagingSource` or `RemoteMediator` in repositories; map entities/DTOs to domain before the ViewModel.
- **WorkManager:** enqueue from repositories or use cases when FR requires durable background sync; keep workers thin and delegate to repositories.
- After meaningful edits, walk change impact: API, DTO, mapper, domain, repository, use case, ViewModel, UI, pagination, states, nav, persistence, analytics, Maestro, regression.

## Dependencies

- `android-kotlin`
- `android-architecture`

## Validation

- Repository unit tests with fakes; integration tests when persistence/API changes.

## Anti-patterns

- Loading Compose skills while editing repositories only.

From Kapil-SquareNetra/android-agentic-orchestrator, MIT.

More from Kapil-SquareNetra/android-agentic-orchestrator