cache-request-isolation

What problem does it solve?

This Skill diagnoses and fixes cases where AniTrend renders a blank UI without crashes because offline-first cache identity values collide in the cache_log table. It helps you confirm why Room tables remain empty and ensures the app will actually fetch and persist the missing data for each source variant.

Core Features & Use Cases

• Detect cache_log collisions that cause subsequent source variants to skip network calls with no exceptions.
• Forensic Room and WAL verification by pulling the app databases from a device and checkpointing WAL pages.
• Validate network behavior with Chucker to determine whether the failure happens before requests or during persistence.
• Apply the fix safely by introducing distinct CacheRequest enum values and updating Koin wiring so sidecar sources use the correct cache request.

Quick Start

Use the cache-request-isolation skill to debug a blank AniTrend screen by pulling the Room databases, checking cache_log for request collisions, and then updating CacheRequest and Koin wiring for the affected source variants.