agentsclimarketplace

Crdt visualization pattern

Skill kjuhwa/skills-hub/skills/design/crdt-visualization-pattern

Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.

Install
npx -y skills add kjuhwa/skills-hub --skill crdt-visualization-pattern

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Side-by-side replica panels with convergence indicators for visualizing CRDT state synchronization

SKILL.md

1.6 KB, 280 tokens by cl100k_base, as published. Nobody here has run it

crdt-visualization-pattern

CRDT visualizations should render two or more replica panels side-by-side, each showing the replica's current local state (counter value, document text, or graph nodes/edges) along with a vector clock or operation log. A central "network" zone between panels visualizes in-flight operations as animated tokens, with controls to pause, reorder, duplicate, or drop messages — this is essential for demonstrating the commutative/idempotent/associative (CIA) properties that define CRDTs. Include a prominent convergence indicator (e.g., a checkmark or colored badge) that turns green only when all replicas report byte-equal state hashes.

For counter-sync visualizations, show per-replica increment histories and the merged sum; for LWW editors, display timestamp tags on each character/field and highlight which writes "won"; for OR-Set graphs, render unique tags (UUIDs) per element-add with strikethrough on tombstoned entries to make add-wins semantics visible. Always expose a "step" mode alongside "auto-play" so users can manually trigger each merge and observe state deltas.

Include a timeline/event-log panel at the bottom showing the global operation order as perceived by each replica — this makes divergence obvious during partitions and convergence dramatic upon reconnection. Color-code operations by originating replica to track causality visually.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.