mcpField
O
offline-sync-conflict-review

offline-sync-conflict-review

github.com/sylphxaiDevelopment144 installsUpdated today
Repository

About offline-sync-conflict-review

A skill for teams designing offline synchronization and conflict handling. It turns requirements around queues, local data safety, merge policies, and multi-device recovery into implementation and QA artifacts.

Key features

  1. 01Offline and authority requirements
  2. 02Data type and mutation classification
  3. 03Local storage and mutation log planning
  4. 04Merge, retry, and recovery policies
  5. 05Conflict UX and QA scenarios

Use cases

  1. 01Designing offline write queues
  2. 02Choosing conflict rules for shared data
  3. 03Planning recovery across devices
  4. 04Testing sync failures and edge cases

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill offline-sync-conflict-review

After installing, type/offline-sync-conflict-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/offline-sync-conflict-patterns.md

Details

From the project README

Offline Sync Conflict Review

Use this skill to convert a offline queues, sync state, conflict resolution, local data safety, and multi-device recovery question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify user job, entity types, mutation types, offline duration, device count, authority model, and harm from wrong merge.
  2. Read references/offline-sync-conflict-patterns.md.
  3. Classify data as append-only, editable profile, collaborative document, financial/legal, media attachment, or system setting.
  4. Define local storage, mutation log, idempotency, ordering, tombstones, merge policy, conflict UI, retry, and recovery telemetry.
  5. Produce sync state machine, conflict decision table, event schema, UX copy, and QA scenario checklist.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not use last-write-wins for money, permissions, legal records, inventory, or destructive actions without explicit product acceptance.
  • Do not silently overwrite another device or collaborator when a user decision is required.
  • Do not queue unbounded offline writes without storage limits, backpressure, and failure UI.
  • Do not claim “offline ready” unless cold start, logout, app reinstall, expired auth, and attachment failures are considered.

Output format

Offline context:
Entity / mutation / harm if wrong:

Sync and conflict plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Merge policy:
- <item> -> <policy, metric, edge case, support note>

Recovery and QA:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported