amey-thakur/ai-skills/collaborative-editing-models
Claude Code and agent skill by amey-thakur/ai-skills
- community
Checking that the SKILL.md file is still in the repository.
Choose between operational transformation, CRDTs, and locking for multi-user editing, and understand what each costs. Use when more than one person can edit the same document at the same time.
Install
npx vskill@latest install amey-thakur/ai-skills/collaborative-editing-modelsSKILL.md
The same SKILL.md was published earlier as amey-thakur/ai-skills/collaborative-editing-models.
Collaborative editing models
Concurrent editing has three honest answers: prevent it with locks, transform operations against each other, or use data types that merge by construction. Each is a different set of trade-offs, and picking by fashion rather than by requirement is why these projects overrun.
Method
- Ask whether you need concurrency at all. Document locking or
section-level checkout is unfashionable and completely adequate when simultaneous edits are rare, at a fraction of the complexity.
- Understand what OT requires. Operational transformation needs a
central server to order operations and transform functions that are correct for every operation pair, which is hard to get right and proven in practice.
- Understand what CRDTs cost. They merge without a coordinating
server and carry metadata that grows with edit history, so memory and payload size become the engineering problem instead of correctness.
- Model intent, not keystrokes. An operation that says insert at
this position survives concurrency far worse than one that says insert after this anchor, which is why anchors matter more than the algorithm choice.
- Decide what merging cannot fix. Two people rewriting the same
paragraph produce a syntactically merged result that reads as nonsense, so some conflicts need a human (see conflict-resolution-ux).
- Use a proven library. Both OT and CRDT implementations are
subtle, heavily tested, and not worth reimplementing for a product feature.
- Test with adversarial concurrency. Simultaneous edits at the same
position, offline divergence, and reconnection are where these systems fail, and they need deliberate tests (see offline-sync).
Boundaries
- These models converge state; they do not guarantee the converged
state is meaningful to users.
- Rich structure such as tables and nested lists is substantially harder
than plain text in every model.
- Access control and permissions are separate concerns that neither
model addresses (see authz-design).
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/realtime-collaboration/collaborative-editing-models/SKILL.md
Popularity
- Repository stars
- 10
- Repository forks
- 2
- 7-day trend score
- 17
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/amey-thakur/ai-skills/collaborative-editing-models)