sync-and-live

Coordinate snapshots, cursors, pulls, pushes, and mutations for offline-first data stores.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/mambisi/pocopine-skills --skill sync-and-live
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-and-live
Source: https://github.com/mambisi/pocopine-skills/tree/main/sync-and-live
Command: npx skills add https://github.com/mambisi/pocopine-skills --skill sync-and-live

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pocopine, SyncServer, Source, query_client_plugin, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables the development of offline-first data sync features and live invalidation in Pocopine applications, allowing for offline persistence and real-time data updates.

Core Features & Use Cases

  • Offline-first Data Sync: Implement sync streams, mutations, subscriptions, and multi-tenant filtered queries with local persistence.
  • Live Invalidation: Integrate wake-up channels for real-time updates without polling.
  • Use Case: Create a multi-tenant application that needs to maintain local data consistency while being updated in real-time by a server.

Quick Start

Use the sync-and-live skill to set up offline data sync for your application.

Frequently Asked Questions about sync-and-live

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

FAQPage Schema
How do I implement offline-first data sync in a multi-tenant application?▼

Offline-first data sync is implemented by coordinating snapshots, cursors, pulls, and pushes for client-side stores. This Skill manages mutation deduplication and conflict handling to maintain local persistence and multi-tenant filtered queries.

How does live invalidation work without polling for real-time updates?▼

Live invalidation works by integrating Server-Sent Events (SSE) wake-up channels to push real-time updates. This mechanism triggers reactive model updates without requiring continuous client-side polling.

Do I need a Rust-based server to use offline-first data sync and live invalidation?▼

Yes, you need a Rust-based server-side implementation. The sync architecture requires query-aware data sources and local storage backends, alongside the Pocopine framework, to function correctly.

What is the best way to handle mutation deduplication and conflict resolution for local data stores?▼

The best way to handle mutation deduplication and conflict resolution is by coordinating sync streams and mutations through a dedicated query client plugin. This ensures data consistency between offline persistence and server pushes.

Can I use Pocopine for multi-tenant filtered queries with local persistence?▼

Yes, Pocopine supports multi-tenant filtered queries with local persistence. The Skill coordinates subscriptions and sync streams to maintain data consistency across tenants even when offline.

What are the limitations of using SSE wake-ups for reactive model updates?▼

SSE wake-ups for reactive model updates require an active connection to deliver real-time invalidation. When offline, the system relies entirely on local storage backends and mutation deduplication until connectivity is restored.