← ClaudeAtlas

appflowy-foundationlisted

Use when porting AppFlowy's offline-first sync kernels — assembling CRDT objects with disk persistence and cloud sync, routing typed events across an FFI boundary, running QoS background task queues, reconnecting realtime sockets, or implementing a local server that satisfies cloud traits without a backend.
ryan-brosas/universal-template · ★ 1 · AI & Automation · score 61
Install: claude install-skill ryan-brosas/universal-template
# AppFlowy: local-first collaborative workspace foundation ## Foundation contract This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships. ## Provenance and revision - Source record: `appflowy`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index. - Recorded revision: `main@5cf3a365dec0d59f64bad1ee4bb1050471a39b93`. - Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`. ## Topic map - Representative topics: Collab assembly; Document lifecycle; Event dispatch; Background tasks; Realtime & offline; Identity & plumbing. - Scope and retrieval questions: `references/index.md#use-this-for`. - Complete capsule chooser: `references/index.md#load-the-matching-source-dump`. - Detailed grouped map: `references/index.md#capsule-map`. - Source limitations and portability boundaries: `references/index.md#boundaries`. ## Retrieval Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.