Architecture Crdts
Use when the user asks about CRDTs, real-time collaborative editing, Yjs, Automerge, Loro, local-first apps, offline sync with automatic merge or OT vs CRDT. Produces CRDT type and library choice, sync and persistence architecture. Not for consensus-based consistency (use distributed-consensus) or offline caching without concurrent edits (use mobile-offline-first).
Install
npx skills add j4flmao/agent-skills --skill architecture-crdtsgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/architecture/crdts ~/.claude/skills/architecture-crdtsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Conflict-free Replicated Data Types (CRDTs)
## Purpose
CRDTs let replicas accept writes independently (offline, peer-to-peer, multi-region) and still converge to the same state once they have seen the same updates, with no central lock or transform server. They trade some storage and semantic control for availability and simple sync. Use proven libraries; design the document model, sync transport, persistence, and access control around them.
## Agent Protocol
### Trigger
"CRDT", "collaborative editor", "multiplayer editing", "Yjs", "Automerge", "Loro", "local-first", "offline merge", "OT vs CRDT", "conflict resolution without server".
### Input Context
- Data shape (text, rich text, lists, maps, counters, trees/canvas).
- Concurrency: number of simultaneous editors, offline duration.
- Topology: client-server relay, peer-to-peer, multi-region servers.
- Auth model and audit/history requirements.
### Output Artifact
CRDT design: per-field type, library choice, sync/persistence architecture, compaction and auth plan.
### Response Format
```
Document model: {field: CRDT type}
Library: {Yjs|Automerge|Loro} Transport: {WebSocket relay|WebRTC|HTTP sync}
Persistence: {updates log + snapshots} Compaction: {policy}
Auth: {room-level|server-validated updates}
Semantics caveats: {e.g. LWW on title, interleaving}
```
### Completion Criteria
- [ ] Each field's merge semantics stated (what happens on concurrent edits).
- [ ] Server validates who may write which document.Details
- Skill name
architecture-crdts- Repository
- j4flmao/agent-skills
- Path
skills/architecture/crdts/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Architecture Crdts skill do?
Use when the user asks about CRDTs, real-time collaborative editing, Yjs, Automerge, Loro, local-first apps, offline sync with automatic merge or OT vs CRDT. Produces CRDT type and library choice, sync and persistence architecture. Not for consensus-based consistency (use distributed-consensus) or offline caching without concurrent edits (use mobile-offline-first).
How do I install the Architecture Crdts skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill architecture-crdts. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Architecture Crdts popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Architecture Domain Driven Design
45j4flmao/agent-skills
Use when the user asks about DDD, domain-driven design, bounded contexts, aggregates and aggregate roots, ubiquitous language, context maps, anti-corruption layers, event storming or value objects. Produces strategic and tactical domain models. Not for simple CRUD apps or folder layering (use backend-clean-architecture) or service decomposition (use microservices).
API Product Management
45j4flmao/agent-skills
Use when the user asks about API as a product, API strategy, API monetization, developer portal, API lifecycle or developer experience metrics. Produces an API product plan with tiers, onboarding and lifecycle policy. Not for endpoint design (use backend-api-design) or versioning mechanics (use backend-api-versioning).
Architecture Postgresql Internals
45j4flmao/agent-skills
Use when the user asks about Postgres MVCC, the write-ahead log (WAL), table bloat, autovacuum, dead tuples, transaction ID wraparound, checkpoints, HOT updates, EXPLAIN ANALYZE or why Postgres is slow. Produces diagnosis queries and tuning settings. Not for schema design (use data-relational-database) or sharding (use architecture-database-scaling).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.