data-android-infrastructure

Document AniTrend's shared Android data infrastructure for controller, strategy, Koin wiring, caching, and database plumbing.

51|6|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/AniTrend/anitrend-v2 --skill data-android-infrastructure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-android-infrastructure
Source: https://github.com/AniTrend/anitrend-v2/tree/main/.agents/skills/data-android-infrastructure
Command: npx skills add https://github.com/AniTrend/anitrend-v2 --skill data-android-infrastructure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes repetitive, error-prone setup by documenting the shared Android data infrastructure that powers the rest of AniTrend’s data modules.

Core Features & Use Cases

  • Shared controller pipeline: Explains how GraphQLController and DefaultController structure request execution and response handling across modules.
  • Consistent online/offline strategy: Clarifies how ControllerStrategy, OnlineStrategy, and OfflineStrategy standardize connectivity checks, error mapping, and callback success/failure signaling.
  • Centralized Koin wiring helpers: Documents ScopeExtensions that reduce controller-construction boilerplate and keep dependency injection consistent.
  • Shared caching and database base: Covers ICacheStore/CacheDao and database helpers used as transitive infrastructure for data modules.

Quick Start

Tell the AI: “Explain how to choose OnlineStrategy versus OfflineStrategy for a new data source and which ScopeExtensions to use for Koin wiring of the correct controller.”

Frequently Asked Questions about data-android-infrastructure

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

FAQPage Schema
How do I standardize GraphQL and non-GraphQL request pipelines in Android?

Standardize Android request pipelines using GraphQLController and DefaultController to structure execution and response handling, applying ControllerStrategy with RequestCallback and DataState semantics for consistent connectivity-aware data flows.

How do I handle online and offline caching strategies for Android data sources?

Handle Android connectivity-aware execution by implementing OnlineStrategy and OfflineStrategy to standardize connectivity checks, map errors, and signal callback success or failure before integrating local cache sources.

What's the best way to wire Koin dependency injection for Android data controllers?

Wire Koin dependency injection for Android data controllers using ScopeExtensions helpers like graphQLController and defaultController to reduce boilerplate and maintain consistent controller construction across modules.

Can I use existing database helpers and caching for new Android data modules?

Yes, you can leverage shared ICacheStore, CacheDao, and database helpers as transitive infrastructure to provide offline caching and local source integration for any new Android data modules.

What do I need to know before implementing a new Android data module with this infrastructure?

Implementing a new Android data module requires understanding ControllerStrategy with RequestCallback and DataState semantics, plus correct use of ScopeExtensions helpers for Koin wiring and connectivity-aware execution.