Android Data Layer

new-silvermoon/awesome-android-agent-skills

This walks you through setting up an offline-first data layer with the Repository pattern as your single source of truth, Room for local persistence, and Retrofit for network calls. It covers the stale-while-revalidate pattern for reads (show cached data immediately, refresh in background) and touches on the outbox pattern for syncing writes. You'll use this when building any Android app that needs to work offline or reduce loading states by caching aggressively. The code examples are straightforward, showing a repository that exposes Room's Flow for reactive updates and a separate sync method for fetching fresh data. It assumes you're already using Hilt for dependency injection and doesn't dive deep into conflict resolution or advanced sync scenarios.

skills.sh installs: 531
GitHub stars: 1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add new-silvermoon/awesome-android-agent-skills --skill android-data-layer --agent claude-code

Installs into .claude/skills of the current project.

Files

Android Data Layer & Offline-First

Instructions

The Data Layer coordinates data from multiple sources.

1. Repository Pattern

Role: Single Source of Truth (SSOT).
Logic: The repository decides whether to return cached data or fetch fresh data.

Implementation:

class NewsRepository @Inject constructor(
    private val newsDao: NewsDao,
    private val newsApi: NewsApi
) {
    // Expose data from Local DB as the source of truth
    val newsStream: Flow<List<News>> = newsDao.getAllNews()

    // Sync operation
    suspend fun refreshNews() {
        val remoteNews = newsApi.fetchLatest()
        newsDao.insertAll(remoteNews)
    }
}