loro

Guide CRDT container selection, sync design, and editor integration for local-first apps.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/fycd2006/studio --skill loro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loro
Source: https://github.com/fycd2006/studio/tree/main/.agents/skills/loro
Command: npx skills add https://github.com/fycd2006/studio --skill loro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enable teams to build robust local-first collaboration by providing a structured guide for selecting CRDT containers, designing sync and versioning, and integrating editors and state mirroring.

Core Features & Use Cases

  • Comprehensive routing to reference material for container choice (LoroMap, LoroList, LoroText), sync/versioning, editor bindings, and app-state mirroring.
  • Practical decision guidance for CRDT fit, architecture tradeoffs, and performance considerations across offline-first scenarios.
  • Use Case: teams building multi-device document editors can follow the routes to implement deterministic merging, conflict resolution, and stable UI state.

Quick Start

Start by loading the primary chapter on containers-and-encoding, then consult fit-and-architecture for high-level tradeoffs and mirror-and-react for UI state mirroring when integrating with the frontend.

Frequently Asked Questions about loro

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

FAQPage Schema
How do I build local-first collaborative apps with offline sync using CRDTs?

Local-first collaboration uses CRDTs to enable deterministic multi-device sync and conflict resolution. Loro provides container types like LoroMap, LoroText, and LoroList to manage state, supporting offline edits that merge automatically when connectivity returns.

How does CRDT versioning work for multi-device document editors?

CRDT versioning tracks document state changes across devices to ensure deterministic merging without central coordination. Loro structures sync and versioning around its container types, allowing collaborative editors to resolve conflicts and maintain stable UI state.

Can I integrate CRDT state mirroring with React for collaborative UI?

Yes, CRDT state mirroring integrates with React to reflect collaborative document changes in the UI. Loro routes to specific guidance on binding editor state and mirroring app state, ensuring stable UI rendering during multi-device sync.

What's the best way to choose CRDT container types for collaborative state?

Choosing CRDT container types depends on your data structure: LoroMap for keyed objects, LoroList for arrays, and LoroText for rich text. Loro routes to reference material on containers and encoding to guide selection for your offline-first architecture.

Does the Loro WASM binding layer support offline-first web applications?

Yes, the WASM binding layer enables running CRDT-powered collaboration directly in web environments. Loro maintains this binding layer to support local-first apps requiring offline sync, multi-device versioning, and deterministic state merging in browser contexts.

When should I not use CRDTs for local-first collaboration?

CRDTs may add overhead for apps needing simple last-write-wins sync rather than granular conflict resolution. Loro provides fit-and-architecture guidance to evaluate tradeoffs, helping determine if CRDT-based collaboration suits your performance and offline-first requirements.