offline-sync

Solid

Offline resilience and sync

AI & Automation 91 stars 13 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Offline and Sync - Queue mutations when offline and replay on reconnect; every queued action is idempotent or deduplicated. - Show sync status honestly: pending, syncing, failed — never pretend an unsynced change is saved. - Resolve conflicts with last-write-wins or explicit user choice; pick one per data type and document it in the task. - Reads degrade gracefully: cached data with a staleness indicator beats a spinner that never resolves.

Details

Author: makifbaysal
Repository: makifbaysal/tasktrooper
Created: 1 weeks ago
Last Updated: today
Language: Go
License: Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

design-offline-sync

Design an offline sync and conflict protocol that preserves user intent across retries, multi-device edits, deletion, and partial failure. Use when offline is a declared product capability. Do not use for ordinary online CRUD or for a live incident.

1 Updated today

SylphxAI

Web & Frontend Listed

android-offline-first-sync

Use this skill whenever building or reviewing an Android feature that involves offline-first data (DB as source of truth), periodic/background sync (WorkManager), cache staleness/TTL policy, or condition-based alerts/notifications (e.g. extreme weather, price drops, stock-outs, low battery). Trigger this for ANY Android app domain — weather, fitness, news, finance, IoT, delivery tracking — not just weather specifically. Also trigger when the user mentions "offline mode", "offline-first", "cache invalidation", "periodic sync", "background refresh", "stale data", "sync status", "WorkManager", or "alert system" in an Android/Kotlin context. This is a feature/capability skill (the pattern of HOW to build the behavior), not a tech-stack tutorial — pair it with whatever networking/DB/DI libraries the project already uses.

0 Updated 2 months ago

rajedev

AI & Automation Listed

async-state-consistency

Asynchronous state consistency: cache races, subscriber notifications, memoized/coalesced loads, replay, one-shot reads, invalidation, stale results. Excludes UI-only display, deployment topology, distributed consensus, unrelated flakiness.

11 Updated 1 months ago

Xopoko