coherence-sync-field-ordering

SKILLWorkflowcommunity
v0.0.0cmitchellVFSUnknownSource →

Use when a coherence [Sync] field's value depends on another synced field — derived/computed synced values that come out wrong on remotes, intermittent desync when several fields change in the same packet, or a [Sync] setter that reads a sibling synced field. Covers why setters have no cross-field o

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
Skill
AuthorcmitchellVFS
Version0.0.0
LicenseUnknown
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Use when a coherence [Sync] field's value depends on another synced field — derived/computed synced values that come out wrong on remotes, intermittent desync when several fields change in the same packet, or a [Sync] setter that reads a sibling synced field. Covers why setters have no cross-field ordering guarantee and the four safe patterns for dependent values.

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.