What problem does it solve? Implementing a feature in a native Kotlin Android app touches many layers — Compose UI, ViewModel state, repository, sync workers, and backend contracts — and it is easy to silently move business logic onto the device or leave failure cases unhandled. This Skill enforces a flat, server-authoritative architecture: the backend decides, the local replica is what the UI observes, and every missing backend capability becomes a recorded handoff artifact instead of a client-side workaround. ## Core Features & Use Cases - Seven-step gated implementation: feature contract, flat-layer placement test, state and data model design, backend-requirement capture, bottom-up implementation, state-focused JVM tests, and a release-readiness gate (R8 release build, lint, device smoke, process death). - Backend gap handoff: missing API capabilities are written as nine-section BR-<n> artifacts in project/backend-requirements/ with a proposed OpenAPI fragment, never worked around on the device. - Failure and offline handling: all eight backend-contract outcome cases mapped into a closed result type, staleness and pending-write states, WorkManager-based queued writes with capped backoff, jitter, and deadlines. - Use Case: Ask to wire a new screen to a REST API with offline support; the Skill designs the state model, generates the client from the OpenAPI contract, implements repository and ViewModel, delegates the Compose UI, and closes with a green release build. ## Quick Start Ask the assistant to implement a feature in your Android app, for example: implement the orders list screen wired to the backend API with offline caching and queued writes.
