realtime-collaboration-engineering
v0.1.2Realtime-collaboration-engineering team — agents (collab-architect, sync-engine-engineer, presence-and-transport-engineer) for multiplayer / collaborative-editing systems (Figma/Notion/Docs): the merge model (CRDT vs OT vs last-writer-wins, by data shape), the shared-document model, offline edits + reconnection/merge, presence & awareness kept OUT of the persisted document, transport (WebSocket vs WebRTC, client-server vs SFU vs mesh), and scaling the sync server (doc sharding, snapshots/compaction, access control at the boundary). skills, a knowledge bank (CRDT-vs-OT + transport/topology Mermaid trees, durable consistency concepts, a dated 2026 tooling map), best-practices, templates, commands, an advisory hook. Engineering craft, not legal/product advice; library specifics carry a date + verify-at-use. Seams: UI -> frontend-engineering; sync service/store -> backend-engineering; op-log fan-out -> data-streaming-engineering; latency -> performance-engineering. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install realtime-collaboration-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install realtime-collaboration-engineering@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/realtime-collaboration-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/build-presence-and-awareness/SKILL.md├── skills/choose-crdt-or-ot/SKILL.md├── skills/design-the-document-model/SKILL.md├── skills/handle-offline-and-reconnection/SKILL.md└── skills/scale-the-sync-server/SKILL.md
Included Skills5
Build live cursors, selections, and who's-here as an EPHEMERAL channel separate from the persisted document: last-write-wins per client, throttled, expiring on disconnect. Never write presence into the CRDT/OT log — it corrupts undo and bloats history.
Choose the merge model for a collaborative feature: CRDT vs OT vs last-writer-wins, decided by whether the system must converge without a central order (offline/P2P) and by the data shape — not by hype. Name the consistency guarantee and the growth-bounding obligation that comes with the choice.
Map the app's shared state onto CRDT/OT primitives per field — sequence for text/lists, map for records, register for scalars, counter for tallies, OR-Set for membership — so the merged result preserves intention, not just converges. Choose each field's type for the conflict you want.
Design the offline-edit and reconnection path: buffer local ops with stable causal identity while disconnected, resume from the last acknowledged version on reconnect, and merge the delta — never replay offline edits as brand-new. The reconnect merge is where naive builds lose data.
Scale a realtime sync server: shard by document/room with connection affinity, fan-out ops within a room, offload snapshots to durable storage, bound document growth (tombstone GC + compaction), and enforce access control at the sync boundary. Horizontal scale is more rooms, not a bigger single node.
Plugin manifests1
{
"name": "realtime-collaboration-engineering",
"version": "0.1.2",
"description": "Realtime-collaboration-engineering team — agents (collab-architect, sync-engine-engineer, presence-and-transport-engineer) for multiplayer / collaborative-editing systems (Figma/Notion/Docs): the merge model (CRDT vs OT vs last-writer-wins, by data shape), the shared-document model, offline edits + reconnection/merge, presence & awareness kept OUT of the persisted document, transport (WebSocket vs WebRTC, client-server vs SFU vs mesh), and scaling the sync server (doc sharding, snapshots/compaction, access control at the boundary). skills, a knowledge bank (CRDT-vs-OT + transport/topology Mermaid trees, durable consistency concepts, a dated 2026 tooling map), best-practices, templates, commands, an advisory hook. Engineering craft, not legal/product advice; library specifics carry a date + verify-at-use. Seams: UI -> frontend-engineering; sync service/store -> backend-engineering; op-log fan-out -> data-streaming-engineering; latency -> performance-engineering. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"realtime-collaboration",
"collaborative-editing",
"multiplayer",
"crdt",
"operational-transform",
"yjs",
"automerge",
"presence",
"awareness",
"websocket",
"webrtc",
"offline-first",
"conflict-resolution",
"sync-engine",
"eventual-consistency"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[realtime-collaboration-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/realtime-collaboration-engineering)